Difference between revisions of "Bugmasters/Marking bugs for the Firefox 57 release"

Revision as of 23:18, 5 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.

How to add the Status and Release Tracking Flags

1. Click Edit Bug
2. Open the Firefox Tracking Flags section if not open
3. Under the Tracking column, select ? for firefox57
4. Under the Status section, select affected for firefox57
5. 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
6. Click Save Changes
7. Release management will review your request to track

How to mark a bug as a Regression

1. Click Edit Bug
2. Open the Tracking section if not open
3. Click into the Keywords field and begin typing regression, it will autocomplete
4. Select regression from the dropdown
5. 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
6. 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.
7. Don't forget to add the Firefox 57 status and tracking flags (see above)
8. Click Save Changes

Useful Bugzilla Queries

• Bugs created on or after 2017-08-02 (start of FFx57 cycle) with status-firefox57 = affected
• Bugs created on or after 2017-08-02 with tracking-firefox57 = ?