Difference between revisions of "Bugmasters/Marking bugs for the Firefox 57 release"
From MozillaWiki
(Add guidance on enhancements) |
(updating) |
||
| Line 5: | Line 5: | ||
[https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html You need the EDITBUGS privilege to do this]. | [https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html You need the EDITBUGS privilege to do this]. | ||
| − | {{Warning|Refrain from promoting bugs filed earlier than the start of the Firefox | + | == Bugs needing a decision == |
| + | |||
| + | Bugs in need of a [https://mzl.la/2eTFgYF decision for Firefox 57]. | ||
| + | |||
| + | {{Warning|Refrain from promoting bugs filed earlier than the start of the Firefox 56 release cycle (2017-06-12.)}} | ||
== How to add the Status and Release Tracking Flags == | == How to add the Status and Release Tracking Flags == | ||
| Line 39: | Line 43: | ||
== Enhancement/Feature Request == | == Enhancement/Feature Request == | ||
| − | Bugs which are requests for enhancements or new features should be marked as severity = enhancement. | + | Bugs which are requests for enhancements or new features should be marked as severity = enhancement. This will remove them from the list of bugs which need a decision for 57. |
== Useful Bugzilla Queries == | == Useful Bugzilla Queries == | ||
Revision as of 00:04, 13 September 2017
The bug that will overshadow all the hard work we put into the Firefox 57 release has probably already been filed. We need to find it and fix it.
If you think a bug might affect users in the 57 release, please set the correct Firefox versions affected in the bug, and then set the tracking-request flag to request tracking of bug by release management team.
You need the EDITBUGS privilege to do this.
Contents
Bugs needing a decision
Bugs in need of a decision for Firefox 57.
Warning: Refrain from promoting bugs filed earlier than the start of the Firefox 56 release cycle (2017-06-12.)How to add the Status and Release Tracking Flags
- Click Edit Bug
- Under the Firefox Tracking Flags section, in the Status column, select affected for firefox57
- If you know that other versions of Firefox are affected/unaffected, please mark them as such
- Click Save Changes
- Only if you think this needs fast escalation: request tracking
- Open the Firefox Tracking Flags section if not open
- Under the Tracking column, select ? for firefox57
- Finish the comment started for you about why this bug should be tracked for release
- What users will be affected
- How many users could be affected
- Release management will review your request to track
How to mark a bug as a Regression
- Click Edit Bug
- Open the Tracking section if not open
- Click into the Keywords field and begin typing regression, it will autocomplete
- Select regression from the dropdown
- If you do not know which patch caused the bug
- Type a comma in the keywords field, and start typing regressionwindow-wanted
- Select regressionwindow-wanted
- If you know which patch caused the bug
- Add the link to the commit as a comment, stating that you believe this is the commit responsible. If you are reasonably sure, make the regression bug block the bug that introduced the regression.
- Don't forget to add the Firefox 57 status and tracking flags (see above)
- Click Save Changes
Enhancement/Feature Request
Bugs which are requests for enhancements or new features should be marked as severity = enhancement. This will remove them from the list of bugs which need a decision for 57.
