Status Update: Firefox 3.5 RC Code Freeze and tree rules

[Mike Beltzner]

followup-to: mozilla.dev.planning
reply-to: dev-pl...@lists.mozilla.org

We're very close to being done with Firefox 3.5 / Gecko 1.9.1
blockers, and the pace has been incredible. Presently we're down to
just over 20 blocking bugs without code fixes:

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=flag%3Ablocking-firefox3.5%252B%2Cblocking1.9.1%252B%20product:Firefox,Core,Toolkit,NSS,NSPR

Many of these bugs have patches that are awaiting review or a revised
patch based on review comments.

Until these 20 or so fixes have landed on mozilla-central, we will be
keeping that tree restricted to:

- patches that fix bugs on that list
- patches that have been marked with approval191+
- patches with explicit driver approval
- patches that are not part of the Firefox build, bustage fixes or
test additions

Developers should be focusing their efforts on getting the fixes for
those issues on mozilla-central as soon as possible.

The mozilla-1.9.1 tree continues to be closed to everything other than
patches that fix blockers and patches that have "baked" on mozilla-
central and are marked approval1.9.1+. Priority should be given to
landing the 30 or so patches which fix blockers, and which have
already landed on mozilla-central but have not yet made it to
mozilla-1.9.1

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=FIXED%20product:Firefox,Core,Toolkit,NSS,NSPR%20flag:blocking-firefox3.5%2b,blocking1.9.1%2b%20-kw:fixed1.9.1,verified1.9.1%20-resolution:INVA,INCO,WORKS,WONT,MOVED,EXPIRED,DUPL

Tomorrow I and others will continue to make decisions about blocking
nominations, approvals and code freeze cutoffs in #shiretoko on
irc.mozilla.org. The active sheriff will be helping you determine if
your patch can be checked in in #developers.

Please let me know if you have any questions.

cheers,
mike

[Tim Riley]

Let the QA team know if you need any help with steps to reproduce,
regression ranges, testing patches, etc. The best way to catch us,
since time is short, is ask in #qa or ping myself (timr), tchung,
ctalbert, or your favorite testing person. If one of us can't do it, we
will find someone that can!

--Tim