550
edits
Bug Triage/Process/Triage: Difference between revisions
→What About Release Status (status_firefoxNN) Flags: start trying to explain how release status works with all this
(→Questions: fix typo) |
(→What About Release Status (status_firefoxNN) Flags: start trying to explain how release status works with all this) |
||
| Line 39: | Line 39: | ||
;P5: Will not fix, but will accept a patch | ;P5: Will not fix, but will accept a patch | ||
== What About Release Status (< | == What About Release Status (<code>status_firefoxNN</code>) Flags == | ||
Release status (and tracking) flags are set independent of triage decisions, but should be consistent with triage decisions. | |||
If an unresolved bug is marked <code>status_firefoxNN = affected</code> then <code>priority = P1</code> should be true. | |||
This relationship is ''not'' transitive. | |||
If a bug is triaged as P1, its status may be one of <code>affected</code>, <code>wontfix</code>, <code>fix-optional</code>, <code>disabled</code> as well. | |||
Also, as a release approaches, the release status of open, high priority (P1) bugs can change. Triagers and engineering leads ''must'' review open bugs with a release status of <code>affected</code> and <code>fix_optional</code>, and decide which of these to keep, and move the others to <code>wontfix</code> for the current cycle. | |||
Use the shared query [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Planned%20Fixes%20for%20Next%20Release&list_id=13846696 Planned Fixes for Next Release] to review these, and move the ones which make sense to [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Planned%20Fixes%20for%20Current%20Cycle&list_id=13846701 Planned Fixeds for Current Cycle]. | |||
An explanation of the [[Bugmasters/Process/Triage/Release_Status | release status field]]. | |||
== How Do I Handle Edge Cases == | == How Do I Handle Edge Cases == | ||