Firefox 3.1/Gecko 1.9.1 Beta 1 Freeze Date
Damon Sicore
We've discussed this a bit already, but I think it makes sense to nail
down a date for the Beta 1 freeze date. Beta 1 is a feature freeze,
so if you have a feature you are working on, it's time to start
wrapping it up. After discussing dates with quite a few people and
hearing people ask for more time, August 19th seems appropriate.
That's a Tuesday, and we can take a look in that day's Firefox 3.1
meeting to see where things stand. Any concerns regarding this date?
Other things I'm noticing/watching/obsessing over:
* There's still about 20 blockers for 3.1/1.9.1. We need to hit that
list pretty hard over the next two weeks. Since blocking+ really
means blocking, those items need to be cleared before final. For the
3.0 betas, we had blockers that lasted past and into betas, so I think
it still make sense to continue doing the same--not all blockers will
be resolved before beta.
* There's about 89 or so blocking noms for 1.9.1. We gotta hammer
through those, ASAP.
* I think we need to run through security bugs and see what we can
fix, even if it means putting off a feature or two until the next
release. I'll continue to bring up specific security bugs with people
directly, but we need others to help out.
* Any feedback so far from Alpha 1 that needs our immediate attention?
I'm very interested to hear what others think, so please speak up if
you have other concerns.
After seeing all the fantastic progress demoed at the summit, I'm
super excited about what's building up to being a great release!
Cheers,
Damon
Axel Hecht
> All,
>
> We've discussed this a bit already, but I think it makes sense to nail
> down a date for the Beta 1 freeze date. Beta 1 is a feature freeze, so
> if you have a feature you are working on, it's time to start wrapping it
> up. After discussing dates with quite a few people and hearing people
> ask for more time, August 19th seems appropriate. That's a Tuesday, and
> we can take a look in that day's Firefox 3.1 meeting to see where things
> stand. Any concerns regarding this date?
We don't have l10n builds, and Aravind is on vacation this week, who's a
key player in setting things up on the hg server. I didn't catch up with
reed today if the one thing that Aravind fixed last weekend was the only
roadblock.
There's no build infrastructure for l10n so far either, i.e., no
tinderboxens etc.
I did talk to beltzner last week and moved this out of panic mode as I
expected the freeze to be further out.
If we depend on Aravind, we'll be down to a week of teaching all our
localization teams how to use hg, which doesn't make me too optimistic.
If we don't, we'd have two week with a 3.0.2 release in between, which
is horribly tight still.
Axel
Mike Beltzner
> I did talk to beltzner last week and moved this out of panic mode as I
> expected the freeze to be further out.
We'll be discussing this further in today's Firefox 3.1 / Gecko 1.9.1 meeting, but I heard a few people expressing concern over the planned freeze date. Further, looking at our release calendar, we have a bunch of pressures at the same time:
- Firefox 2.0.0.17 / 3.0.2 updates
- major update to Firefox 3.0.2 (if it's blessed as such)
- we're down a few resources to vacations & moves (thankfully, none to bears)
Our current plan is to co-ordinate 2.0.0.17 and 3.0.2, and make the latter the major update release, but you know how Black Hat week often changes things ... if we need to insert another release, we can expect to be requesting things of fairly crispy Build and QA teams. :)
> If we depend on Aravind, we'll be down to a week of teaching all our
> localization teams how to use hg, which doesn't make me too
> optimistic.
> If we don't, we'd have two week with a 3.0.2 release in between, which
> is horribly tight still.
Can we get something set up immediately that allows us to begin the hg tutorial process, or does that depend on the way in which things are solved?
cheers,
mike
Axel Hecht
Aravind and reed had something which looked like a clean split between
things that Aravind wants to do himself and things that reed could
already get done. I have no clue if
https://bugzilla.mozilla.org/show_bug.cgi?id=439140 covers all that
Aravind wanted to do in person.
Axel
Tony Chung
> ----- "Axel Hecht" <l1...@mozilla.com> wrote:
>
>> I did talk to beltzner last week and moved this out of panic mode as I
>> expected the freeze to be further out.
>
> We'll be discussing this further in today's Firefox 3.1 / Gecko 1.9.1 meeting, but I heard a few people expressing concern over the planned freeze date. Further, looking at our release calendar, we have a bunch of pressures at the same time:
>
> - Firefox 2.0.0.17 / 3.0.2 updates
> - major update to Firefox 3.0.2 (if it's blessed as such)
> - we're down a few resources to vacations & moves (thankfully, none to bears)
>
> Our current plan is to co-ordinate 2.0.0.17 and 3.0.2, and make the latter the major update release, but you know how Black Hat week often changes things ... if we need to insert another release, we can expect to be requesting things of fairly crispy Build and QA teams. :)
>
we'll be a little light on resources during the 2nd half of august
(Tony, sam, Marcia, al -- on vacation).
Mike Beltzner
> Hi there, what is the planned dates for 2.0.0.17 / 3.0.2? For QA,
> we'll be a little light on resources during the 2nd half of august
> (Tony, sam, Marcia, al -- on vacation).
A little off topic for this particular thread, but so you know, Sam
Sidler and I are doing what we can to work those dates out, hunting
estimates from developers and getting the latest Vegas odds on what'll
happen this week. More as we know it, likely in a different thread.
Good to know about you guys being light on resources.
cheers,
mike
Peter Weilbacher
> We've discussed this a bit already, but I think it makes sense to nail
> down a date for the Beta 1 freeze date.
Interesting, when I first read this I never noticed that there won't be
a second alpha. When was it decided to skip that? I try to read up on
meeting minutes and the like but didn't see that. Don't you think that
the media stuff and other new stuff are still to fresh to call it "beta"?
Are you going to rename the nightlies to be b1pre instead of a2pre?
Peter.
Mike Beltzner
In several meetings where we discussed schedule, apologies if notes
were taken poorly.
If the quality of the builds is not what we feel we can call beta, we
won't call it beta.
No.
cheers,
mike