Tree re-opening today for blockers and approved patches
This morning at 11:15am PST the tree was handed to our Build Team for tagging, kicking off the Firefox 3 Beta 4 release process. It will stay closed as the team confirms that the tagging correctly picked up the required pieces to properly perform Profile Guided Optimization (PGO) builds, and re-open later today.
Last week all component owners and drivers re-triaged the blocker lists in order to get a better sense of the remaining work required on Firefox 3 and Gecko 1.9, and which items need wide exposure and testing (marked as P1s) and which need to be fixed before we ship (marked as P2s). The resulting Firefox 3 / Gecko 1.9 Blocker List shows a manageable number of P1 and P2 items, but enough of them to make the release drivers believe that an additional beta is required. The specific schedule for this beta will be discussed at tomorrow’s Firefox 3 / Gecko 1.9 meeting, with release drivers proposing a 2-week development cycle.
As such, when the tree re-opens shortly, it will be under the following rules:
- patches on bugs marked as blocking1.9+ or blocking-firefox3+ may land;
- patches with approval1.9+ may land;
- any patch which changes a string must have approval1.9+ to land and be marked with the late-l10n keyword;
- any patch which may affect add-ons or themes must be marked with the late-compat keyword;
- tests and “not part of the build” patches may land.
(As always, these rules are available on the Tree Status wiki page.)
Developers should focus on blocker bugs first, and bug reporters should feel free to nominate bugs for blocking status and include their rationale and if possible a description of the risk/reward tradeoff for fixing or not fixing the bug.