Hey everyone,
Product drivers met on Friday to discuss the schedule for Firefox
3.0.1, and after taking into consideration the other requirements on
the Build and QA teams we've decided to set a target of next
Wednesday, July 3rd as the start date for generating builds, with code
freeze set for Monday, June 30th at 11:59pm PDT.
If you're assigned to or a reviewer on a bug marked blocking1.9.0.1+
please make this your top priority. Bug lists are available on the
Tinderbox page for the 1.9 branch:
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox
I'll be continuing to do approvals and blocker triage over the weekend.
If we can fix all the bugs marked [MU+] in the whiteboard on this same
schedule, then we will be able to also use Firefox 3.0.1 as a
candidate for a major update offer to all users on the Firefox 2.0.
cheers,
mike
> I'll be continuing to do approvals and blocker triage over the
> weekend.
Note that the Firefox 3.0.x (1.9.0 branch) tree is currently closed due
to the missing (one-and-only) Mac debug/leak machine, so anything
approved isn't going to be able to land until that machine is back.
~reed
--
Reed Loden - <re...@reedloden.com>
> On Sat, 28 Jun 2008 16:58:57 -0400
> Mike Beltzner <belt...@mozilla.com> wrote:
>
>> I'll be continuing to do approvals and blocker triage over the
>> weekend.
>
> Note that the Firefox 3.0.x (1.9.0 branch) tree is currently closed
> due
> to the missing (one-and-only) Mac debug/leak machine, so anything
> approved isn't going to be able to land until that machine is back.
Being tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=438811
for those interested. We'll keep an eye on this and if need to adjust
the schedule, will do so here.
Thanks, Reed.
cheers,
mike
> Mike Beltzner wrote:
>> Product drivers met on Friday to discuss the schedule for Firefox
>> 3.0.1,
>> and after taking into consideration the other requirements on the
>> Build
>> and QA teams we've decided to set a target of next Wednesday, July
>> 3rd
>> as the start date for generating builds, with code freeze set for
>> Monday, June 30th at 11:59pm PDT.
>>
>
> Is that Wednesday, July 2nd or Thursday, July 3rd?
Didn't see a reply here... Mike meant Wednesday, July 2nd.
-Sam
Is this still happening?
When will the tree reopen for 1.9.0.2 and when will the remaining
approvals be processed?
Standard8
> Is this still happening?
We've restored the missing OSX test box and fixed an orange on a Linux
one, but we're still waiting for the Windows PGO box to go green after
being rebooted.
I'm doing approvals, and depending on when the tree creaks open, we
might shift code freeze. We want to have a day of bake time before
starting builds. Watch this space!
> When will the tree reopen for 1.9.0.2 and when will the remaining
> approvals be processed?
As usual, we'll tag and build, and once that's done we'll re-open the
tree for approval1.9.0.2 and do the flag shuffle.
cheers,
mike
Thanks to some heroics from the likes of reed, gavin, ss, dholbert,
and dbaron, we were able to land all the blockers and approved patches
in time for tonight's code freeze. We don't expect there to be any
further problems, and should enter into our bake-time as planned.
>> When will the tree reopen for 1.9.0.2 and when will the remaining
>> approvals be processed?
>
> As usual, we'll tag and build, and once that's done we'll re-open the
> tree for approval1.9.0.2 and do the flag shuffle.
This flag has been created, and I moved all outstanding
approval1.9.0.1? requests to be approval1.9.0.2? In the future I've
decided that we won't do this, and we'll simply write the approvals
query for approval1.9.0.n, where n = the current release and earlier.
That should save everyone on bugmail spam :)
I'm off tomorrow, and ss will be leading the charge forward. Should be
a quiet day of baking as 2.0.0.15 is released, then on to builds for
Thursday AM.
cheers,
mike