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 22:01, 20 September 2017
, 20 September 2017→Bugs needing a decision: update link, add notes on what happens as 57 looms
(→How to mark a bug as a Regression: add link to Ehsan's article) |
(→Bugs needing a decision: update link, add notes on what happens as 57 looms) |
||
| Line 4: | Line 4: | ||
[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]. | ||
== Making decisions as the 57 Beta approaches == | |||
As we review the list of bugs, it's important to mark the status flag (<code>affected</code>, <code>not-affected</code> or <code>wontfix</code>). If something is <code>affected</code>, that means we'd consider an uplift into beta; otherwise it's <code>wontfix</code>. You can label bugs as <code>fix-optional</code> for 57, but those will quickly get converted to <code>wontfix</code>. There will be an approximate 2 week window after uplift where we can get non-catastrophic bugs into Beta. After that 2 week window, the bar will be quite high: i.e. "Will this bug trigger a dot release? If not, it's <code>wontfix</code>." | |||
== Bugs needing a decision == | == Bugs needing a decision == | ||
Bugs in need of a [https://mzl.la/ | Bugs in need of a [https://mzl.la/2fAgqOc decision for Firefox 57]. | ||
{{Warning|Refrain from promoting bugs filed earlier than the start of the Firefox 56 release cycle (2017-06-12.)}} | {{Warning|Refrain from promoting bugs filed earlier than the start of the Firefox 56 release cycle (2017-06-12.)}} | ||