550
edits
Bugmasters/Marking bugs for the Firefox 57 release: Difference between revisions
Jump to navigation
Jump to search
Bugmasters/Marking bugs for the Firefox 57 release (view source)
Revision as of 21:07, 1 September 2017
, 1 September 2017→How to mark a bug as a Regression: regression instructions
(Created page with "'''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 mi...") |
(→How to mark a bug as a Regression: regression instructions) |
||
| Line 19: | Line 19: | ||
# Open the ''Tracking'' section if not open | # Open the ''Tracking'' section if not open | ||
# Click into the ''Keywords'' field and begin typing ''regression'', it will autocomplete | # 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 | |||
# Don't forget to add the Firefox 57 status and tracking flags (see above) | |||