Skip to content

Instantly share code, notes, and snippets.

@EmilyM1
Created March 16, 2022 17:25
Show Gist options
  • Save EmilyM1/4998cb4c3e0b42955be1e2ccb676eef6 to your computer and use it in GitHub Desktop.
Save EmilyM1/4998cb4c3e0b42955be1e2ccb676eef6 to your computer and use it in GitHub Desktop.
Label to backport 3.22
If the Bugzilla associated with the PR has the "FastFix" keyword, the subjective assessment on the issue has already been done and a customer is impacted. These PRs should be prioritized for merge.
verified
does not apply
The bug has significant impact either through severity, reduction in support, or number of users affected.
verified
does not apply
For branches that are in the Maintenance lifecycle phase:
The bug is a critical fix, no reasonable workaround exists, and a recommendation for upgrade has been ruled out, or
The bug is a security related bug
Branch not in maintenance mode yet (current release + previous release for 90 days after current GA; everything older is in maintenance)
The severity field of the bug must be set to accurately reflect criticality.
verified
The PR was created with the cherry-pick bot OR the PR's description is well formed with user-focused release notes that state the bug number, impact, cause, and resolution. Where appropriate, it should also contain information about how a user can identify whether a particular cluster is affected.
verified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment