Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Firefox 2 RC2 Planning

0 views
Skip to first unread message

Mike Schroepfer

unread,
Sep 22, 2006, 9:47:46 PM9/22/06
to
Hi Folks,

We have a handful of bugs that look reasonable to cause a FF2 RC2:

https://bugzilla.mozilla.org/show_bug.cgi?id=353160
https://bugzilla.mozilla.org/show_bug.cgi?id=353264
https://bugzilla.mozilla.org/show_bug.cgi?id=353266

We'd also really like to give the localizer teams time to finish up
their work - especially around the late changing en-US help. Things
such as:

https://bugzilla.mozilla.org/show_bug.cgi?id=353628
https://bugzilla.mozilla.org/show_bug.cgi?id=353467
https://bugzilla.mozilla.org/show_bug.cgi?id=353271
https://bugzilla.mozilla.org/show_bug.cgi?id=353485

Schedule would look like such:

RC1 Release: Tuesday Sept 26
RC2 l10n Freeze: Thurs Sept 28 23:59 PDT
RC2 Code Freeze: Friday Sept 29 09:00 PDT
RC2 Release Target: Fri Oct 6

This schedule is pending feedback from RC1. If we are forced to do
further Release Candidates we will not be taking any more l10n changes.

We are in the end game here - which means days matter and our tolerance
for risk is *zero*. We will not take bugs unless they are of great
benefit: crashes, web compatibility, and major regressions. IMHO FF2
RC1 is already a tremendously superior product to FF15. So let's wrap
this up!

The release drivers will start approving bugs for RC2 by marking 1.8.1+
and commenting "Approved for RC2" in the bug. Triage will continue
daily at 10AM PDT (650) 903-0800x91, conf# 8602. You can join there or
#bonecho if you have any questions.

All the best,

Schrep

Axel Hecht

unread,
Sep 23, 2006, 3:57:19 AM9/23/06
to
Hi,

if you got approval, please check in the approved patches as soon as you
can. Please mention the bug number and the approval in the check-in
comment, and add the fixed1.8.1 keyword to your bug.
Test the following nightly and verify that your bug got fixed, and that
there were no regressions. If everything went fine, mark the bug
VERIFIED, and change the fixed1.8.1 keyword to verified1.8.1.

As you can see, the deadline for l10n is roughly 24 hours before the
main code freeze. We have seen some approved patches busting the tree or
other things slip which required firefighting. That day is for me to
verify which patches landed, and which not, and really sign off on the
tree for release. Note, if you have a patch that got approval and didn't
check it in by Thursday 23:59, that approval is dead and gone. No matter
what the bug flag says at Friday, that approval was an approval to land
by Thursday. This sounds bossy and it is, I want to make everyone
understand that this day is not a grace window, but a bustage fix window.

We have another 5 days to fix bugs, anything that doesn't make it in by
then just can't be that important.

Axel

Axel Hecht

unread,
Sep 23, 2006, 4:07:22 AM9/23/06
to
Actually, just 9 hours. That's gonna be interesting.

Axel

0 new messages