Releases/Flags
Because of current limitations in Bugzilla, we've started using "multi-state flags" in some places and are planning to transition to using them everywhere. This page documents the flags we use (per branch) and how we use them.
Gecko 1.9.3
blocking1.9.3
A multi-state flag that currently has five values which show whether a bug blocks the Gecko 1.9.3 release and, if so, which milestone it blocks.
- ? - This bug has been nominated to block a milestone of Gecko 1.9.3.
- - (minus) - Drivers have determined this bug will not block Gecko 1.9.3.
- alpha1 - This bug blocks the alpha 1 milestone of the Gecko 1.9.3 release.
- beta1 - This bug blocks the beta 1 milestone of the Gecko 1.9.3 release.
- final - This bug blocks the final release of Gecko 1.9.3.
Note: A multi-state status1.9.3 flag does not exist for this Gecko release yet. It will be created after branching from trunk. Status is determined using the regular Bugzilla status and resolution fields.
Gecko 1.9.2
blocking1.9.2
A tri-state flag (?, +, and -) that shows whether a bug blocks the Gecko 1.9.2 release or not.
wanted1.9.2
A tri-state flag (?, +, and -) that shows whether a bug is wanted for the Gecko 1.9.2 release or not.
status1.9.2
A multi-state flag that currently has four values that show the status on the 1.9.2 branch, specifically.
- unaffected - The 1.9.2 branch is not affected by this bug.
- wontfix - There is no intention to fix this on the 1.9.2 branch.
- beta1-fixed - This bug was fixed on the 1.9.2 branch in advance of Gecko 1.9.2 beta 1.
- final-fixed - This bug was fixed on the 1.9.2 branch in advance of Gecko 1.9.2 final but after Gecko 1.9.2 beta 1.
(Additionally, as we get closer to the final release of Gecko 1.9.2, we'll add new options such as "?", "wanted", and ".1-fixed". See the section below on status1.9.1 for how these will be used.)
Gecko 1.9.1
blocking1.9.1
Currently has six values that show whether a bug blocks a specific Gecko 1.9.1 maintenance ("dot") release and, if so, which release it is.
- ? - This bug has been nominated to block a maintenance release of Gecko 1.9.1.
- - (minus) - Drivers have determined this bug will not block a maintenance release of Gecko 1.9.1.
- needed - This bug will block a maintenance release of Gecko 1.9.1, but it is unclear which release it will block.
- .4+ - This bug blocks the Gecko 1.9.1.4 maintenance release.
- .3+ - This bug blocks the Gecko 1.9.1.3 maintenance release.
- .2+ - This bug blocks the Gecko 1.9.1.2 maintenance release.
Note: For Gecko 1.9.1.1, we used a different method to show blocking.
(Each release, we'll add a new option to block the next maintenance release.)
status1.9.1
A multi-state flag that currently has seven values that show the status on the 1.9.1 branch, specifically.
- ? - This bug needs to be triaged on the 1.9.1 branch to determine if it is affected or wanted on that branch.
- unaffected - The 1.9.1 branch is not affected by this bug.
- wontfix - There is no intention to fix this on the 1.9.1 branch.
- wanted - This bug was is considered "wanted" on on the 1.9.1 branch and may or may not block (see the blocking1.9.1 flag).
- .4-fixed - This bug was fixed on the 1.9.1 branch in advance for the Gecko 1.9.1.4 maintenance release.
- .3-fixed - This bug was fixed on the 1.9.1 branch in advance for the Gecko 1.9.1.3 maintenance release.
- .2-fixed - This bug was fixed on the 1.9.1 branch in advance for the Gecko 1.9.1.2 maintenance release.
Note: For Gecko 1.9.1.1, we used a different method to determine fixed status.