Firefox 3 Schedule Update: beta 3 & beyond
Mike Beltzner
In today's Firefox 3 Meeting[1] we took a hard look at the amount of P1
blockers remaining for Beta 3, and the P2 blockers remaining, and
decided that we're still going to do a Beta 3 code freeze tonight, but
will be adding another milestone (Beta 3.1? :) ) before moving on to
Release Candidate builds.
Firefox 3 Beta 3
----------------
There are currently more than 60 bugs marked P1 and blocking-firefox3+
or blocking1.9+ with some target milestone. We need to reduce this list
for code freeze tonight.
If you own one of these bugs, and believe that your feature MUST get
into Firefox 3 Beta 3, please make sure to set the target milestone to
"Firefox 3 Beta 3" or "mozilla1.9 beta 3" (note: these used to be "M11",
but have been renamed). Please do this ASAP.
Code freeze is tonight, chatter is in #granparadiso on IRC. We will be
driving the list of blocking+, P1, target=beta 3 bugs to zero. This
query shows that list:
Tree management after freeze
----------------------------
After tonight's freeze we'll be holding the tree closed to bake the beta
for the rest of the week. During that time we should be focusing on
regression spotting and fixing, and all patches must have explicit
approval using the blocking1.9b3 flag before landing. (This is the same
process we've used in the past two betas)
Assuming all goes well, we'll hand the tree over to the Build team on
Monday to generate Firefox 3 Beta 3 release candidates.
We continue to remain frozen on strings, meaning that any string change
will require the "late-l10n" keyword, and justification for the late
change. We will also require that any changes which could affect add-ons
to be tagged with a "late-compat" keyword so that add-on developers can
keep themselves up to date.
Firefox 3 Beta 4 Schedule
-------------------------
Our goal is to do a quick turnaround on Firefox 3 Beta 4, but we cannot
provide a good estimate until we know the size and scope of blockers
remaining after the Beta 3 codefreeze. To help us, if bug owners of
blocker bugs could add a time estimate using the notation [swag: <time
estimate in days>] in the status whiteboard, that would help a lot.
As soon as we know more about the schedule for this beta, we'll post to
dev-planning.
cheers,
Firefox Release Drivers (mike, mike, mike, damon and vlad)
[1]: http://wiki.mozilla.org/Firefox3/StatusMeetings/2008-01-29
Reed Loden
Mike Beltzner <belt...@mozilla.com> wrote:
> Tree management after freeze
> ----------------------------
> After tonight's freeze we'll be holding the tree closed to bake the
> beta for the rest of the week. During that time we should be focusing
> on regression spotting and fixing, and all patches must have explicit
> approval using the blocking1.9b3 flag before landing. (This is the
> same process we've used in the past two betas)
I believe you meant "approval1.9b3" instead of "blocking1.9b3" above. :)
~reed
--
Reed Loden - <re...@reedloden.com>
Mike Beltzner
> I believe you meant "approval1.9b3" instead of "blocking1.9b3" above. :)
Indeed I did!
Slightly after midnight we froze the tree for beta 3. This means that
from this point on, only patches with approval1.9b3+ will be allowed to
land.
How do you get that flag? Request it, and the Firefox 3 Drivers (schrep,
damons, mconnor, vlad and I) will triage that list twice daily at least.
We're going to be VERY conservative, so the onus will be upon you to
explain in the bug why you believe that the patch *must* be in this
milestone as opposed to waiting for the tree to unfreeze early next week.
cheers,
mike