We're ready to start freezing and closing down for the upcoming
Firefox 3.1 Beta 3. In order to do so, we'll need to lock down the
trees to ensure that we're reducing the churn for the final set of
patches that need to be landed.
As of now, mozilla-central and mozilla-1.9.1 are to be CLOSED for the
following specific set of checkins:
on mozilla-central ...
https://bugzilla.mozilla.org/show_bug.cgi?id=333198
https://bugzilla.mozilla.org/show_bug.cgi?id=479442
https://bugzilla.mozilla.org/show_bug.cgi?id=480767
https://bugzilla.mozilla.org/show_bug.cgi?id=480793
As soon as these land and the trees cycle green, we'll re-open mozilla-
central to regular checkins.
on mozilla-1.9.1 ...
all the above mozilla-central bugs
https://bugzilla.mozilla.org/show_bug.cgi?id=340345
https://bugzilla.mozilla.org/show_bug.cgi?id=479143
https://bugzilla.mozilla.org/show_bug.cgi?id=480579 (t-m merge)
https://bugzilla.mozilla.org/show_bug.cgi?id=476374 (t-m merge)
https://bugzilla.mozilla.org/show_bug.cgi?id=459161 (t-m merge)
After these landings we'll keep the mozilla1.9.1 tree closed to let it
cycle a few times before we spin our builds starting late tonight, PST
(which is midday, NZT!)
cheers,
mike
> As of now, mozilla-central and mozilla-1.9.1 are to be CLOSED for
> the following specific set of checkins:
>
> on mozilla-central ...
> https://bugzilla.mozilla.org/show_bug.cgi?id=333198
> https://bugzilla.mozilla.org/show_bug.cgi?id=479442
> https://bugzilla.mozilla.org/show_bug.cgi?id=480767
> https://bugzilla.mozilla.org/show_bug.cgi?id=480793
>
> As soon as these land and the trees cycle green, we'll re-open
> mozilla-central to regular checkins.
All of these patches have now landed (just need mrbkap to mark his
last one as fixed!). As soon as mozilla-central cycles green (mrbkap
should be watching, at least!), #developers can feel free to re-open
the tree.
There are still 9 bugs that need to land on mozilla-1.9.1 before we
can hand off that tree to Release Engineering to start Firefox 3.1
Beta builds. Those bugs are:
https://bugzilla.mozilla.org/show_bug.cgi?id=459161
https://bugzilla.mozilla.org/show_bug.cgi?id=476374
https://bugzilla.mozilla.org/show_bug.cgi?id=480579
(all of which will be handled by sayrer with a tracemonkey merge)
https://bugzilla.mozilla.org/show_bug.cgi?id=480767
https://bugzilla.mozilla.org/show_bug.cgi?id=480793
https://bugzilla.mozilla.org/show_bug.cgi?id=333198
(all of which are smaug's patches and can be landed by him, bent
or jst)
https://bugzilla.mozilla.org/show_bug.cgi?id=340345
https://bugzilla.mozilla.org/show_bug.cgi?id=479143
(both of these are bent's bugs and can be landed by him or jst)
https://bugzilla.mozilla.org/show_bug.cgi?id=479442
(mrbkap's bug, can be landed by him, bent or jst)
Nick Thomas is standing by to start builds once we land those bugs on
mozilla-1.9.1 and the trees cycle green. I would ask that the people
responsible for those landings reply to this thread as they land their
bugs.
cheers,
mike
> All of these patches have now landed (just need mrbkap to mark his
> last one as fixed!). As soon as mozilla-central cycles green (mrbkap
> should be watching, at least!), #developers can feel free to re-open
> the tree.
The tree cycled green just now, and I have re-opened mozilla-central.
Please (please!) continue to be responsible and if you check something
in, stick around to watch the unit tests cycle before leaving IRC. If
you're not around and an orange can't be explained after your check
in, you will be backed out!
>
The mozilla-1.9.1 tree will remain closed for Beta 3 freeze. There are
now 4 bugs that need to land on mozilla-1.9.1 before we can hand off
that tree to Release Engineering to start Firefox 3.1 Beta builds.
Those bugs are:
Tracemonkey merge ...
https://bugzilla.mozilla.org/show_bug.cgi?id=459161
https://bugzilla.mozilla.org/show_bug.cgi?id=476374
https://bugzilla.mozilla.org/show_bug.cgi?id=480579
Blake ...
https://bugzilla.mozilla.org/show_bug.cgi?id=479442
the follow-up changesets he landed on mozilla-central
(ce00f900e758 and 3d0e0bc6a8c4)
(mrbkap's bug, can be landed by him, bent or jst)
It's now 7:30pm in New Zealand, so we've missed our window with Nick
Thomas. Blake, Rob, please get these fixes landed on 1.9.1 ASAP so we
can start with builds tomorrow.
cheers,
mike
> Tracemonkey merge ...
> https://bugzilla.mozilla.org/show_bug.cgi?id=459161
> https://bugzilla.mozilla.org/show_bug.cgi?id=476374
> https://bugzilla.mozilla.org/show_bug.cgi?id=480579
These landed with http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?changeset=5f88bd7d7899
> Blake ...
> https://bugzilla.mozilla.org/show_bug.cgi?id=479442
> the follow-up changesets he landed on mozilla-central
> (ce00f900e758 and 3d0e0bc6a8c4)
> (mrbkap's bug, can be landed by him, bent or jst)
And this landed with http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?changeset=bb8953ffb790
> It's now 7:30pm in New Zealand, so we've missed our window with Nick
> Thomas. Blake, Rob, please get these fixes landed on 1.9.1 ASAP so
> we can start with builds tomorrow.
The trees have cycled green several times now (aside from an
explainable orange or two) so I think we're ready to hand off to build
at:
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/bb8953ffb790
Once they've tagged & branched, we'll re-open the mozilla-1.9.1 tree
to checkins. Thanks, everyone!
cheers,
mike
> The mozilla-1.9.1 tree will remain closed for Beta 3 freeze. There
> are now 4 bugs that need to land on mozilla-1.9.1 before we can hand
> off that tree to Release Engineering to start Firefox 3.1 Beta
> builds. Those bugs are:
Just to wrap up, last night we tagged and started builds on Firefox
3.1 Beta 3 and re-opened the mozilla-1.9.1 tree. Anyone with:
- patches for bugs that are marked blocking1.9.1+ or blocking-
firefox3.1+, or
- patches marked with approval1.9.1+, or
- patches that add or fix tests or are not part of the Firefox build
may once again check into the mozilla-1.9.1 repository.
cheers,
mike