flag changes coming for this week
To facilitate the triage we’re going to be doing this week for Fx3/1.9 we’ll be making some changes to various flags. There’s a few goals here:
* Identifying the set of bugs that will absolutely block the release of Firefox 3
* From those bugs, identify the set of bugs that we need to ship in a beta to get wider testing before ship.
* Ensure that bugs we won’t get done for this release don’t get lost in the shuffle.
In order to do this, we are going to work against the following plan, starting Real Soon Now:
* The current blocking1.9 flag will be renamed to tracking1.9 on a temporary basis.
* A new blocking1.9 flag will be created, along with a wanted-next flag to track bugs that won’t make 1.9.0 but should be tracked.
* All b4 blockers will move over to the new blocking flag immediately.
* All outstanding nominations against the old blocking flag will be migrated as well.
* Drivers will triage all of the open bugs marked as tracking1.9+, moving flags to one or more of blocking1.9, wanted-next, or wanted1.9.0.x as appropriate. the tracking1.9 flag will be cleared as we go.
* When there are no bugs with the tracking1.9 flag left, we’ll obsolete the flag and rename it to blocking1.9 so historical queries continue to work.
For developers and triagers:
Please don’t be alarmed if your P1/P2 bugs no longer appear as blockers, we’ll be retriaging aggressively and plan to be complete this week. If you have opinions on your bugs, please add comments making your recommendations for drivers.
The new blocking1.9 should be used like the old one, both for nominating blockers for beta 4 and for final. If a bug was previously marked as a blocker but hasn’t been retriaged, please nominate again to expedite the process.
For questions or feedback, please see the matching post in dev.planning.