Firefox 2 Beta 1 Status
Mike Schroepfer
As of this writing the JS 1.7 has landed. The only remaining issues are
the branding changes (BonEcho->Firefox 2) and the pref pane cleanup.
Hopefully these will land tonight - should land no later than early
tomorrow.
Once the last check-in clears our time line is as follows:
Tag and build from tag ~4 hrs
QA team to run BFTs and tests on newer feature areas ~2 days
Repeat as necessary if we need to take regression fixes
Pull and build l10n trees ~4hrs (can happen in parallel with QA)
Once we have a candidate in hand it takes ~24 hours to stage everything
(allowing time for mirror sync, etc) before we can publicize it as live.
Since our window for testing changes before beta 1 is small we’ll only
be accepting patches that truly block the beta - i.e.:
* Major regressions in new functionality
* Anything that prevents wide scale testing of the beta
If you have anything you think fits this category please nominate it for
blocking (blocking-firefox2?) or 1.8.1 (blocking1.8.1?) and set the
target milestone to “Firefox 2 beta1?
There are a long list of blocking bugs which are suitable for inclusion
in beta2. We’ll start approving and landing them once the tree is clear
from beta1.
We’ll continue to do triage sessions daily/twice daily as needed.
Dialin/IRC are same as Bon Echo meetings (866-216-2181/#bonecho). Pop
into IRC anytime if you have questions.
Best,
Schrep
P.S. Thanks to Beltzner for great notes from today’s status meeting:
http://wiki.mozilla.org/Firefox2/StatusMeetings/2006-07-06
in case you want more details.
Axel Hecht
Beta 1 builds on Monday noon UTC. That's 2pm in Berlin, or 5am in
Mountain View.
We hope that localizers will have enough time to get their locales into
shape by then, so that we can have wide testing on the localizations itself.
We look at these l10n builds as Alphas, thus there won't be any Mozilla
QA involved or the like.
Anything that goes green (we may take orange (*), too) for browser and
toolkit by Monday on noon UTC (coincidence? no, I pull the reps on noon
UTC each day) will be part of beta1.
Whether B1 has an impact on a locale shipping with Firefox2 will depend
on quite a few things, most of which remain to be found, AFAICT.
Bottom line, please jump through as many loops as possible to get B1
into good shape.
Axel
PS: (*), orange on that page is different from orange on tinderbox, an
orange tinderbox may likely indicate something stop-ship. Basically,
there shouldn't be entities etc missing from a locale, if there are
unused ones, that's likely OK for B1.
Mike Schroepfer
Just a quick note that we have our first Release Candidates up and
posted on the FTP site (in the nightly/bonecho-beta1-candidates
directory). We will be testing over the weekend and through early next
week (and can use your help for this) - if you see any showstoppers for
the beta1 release please let us know right away by nominating a bug for
1.8.1? or firefox2? with a target milestone.
Best,
Schrep
P.S. Please don't hand the link around as this is only an RC and it
isn't replicated out to our mirror infrastructure.
Mike Beltzner
> and through early next week (and can use your help for this) - if
> you see any showstoppers for the beta1 release please let us know
> right away by nominating a bug for 1.8.1? or firefox2? with a
> target milestone.
For the sake of clarity, any showstopper bugs should be given the
nomination flags that Schrep mentions and a target milestone of
mozilla1.8.1beta1 or Firefox 2 beta1 (depending on the component only
one of those flags will be available).
Also, please use #bonecho on irc.mozilla.org for chatter and
discussion. While I won't be hanging out there all weekend, I'll be
monitoring scrollback, and you can ping me and point me to any issues
that you want to bring to the attention of the 1.8.1 drivers.
Finally, thanks to everyone who helped us wrap up all of the beta1
blockers to date. Rest up this weekend, since next week we'll be
starting down to road torwards beta2!
cheers,
mike
Robert Accettura
>
> P.S. Please don't hand the link around as this is only an RC and it
> isn't replicated out to our mirror infrastructure.
http://digg.com/software/Firefox_2.0_Beta_1_Release_Candidate_Now_Available
Hopefully since it's Saturday, it won't do to much damage.
--
Robert Accettura
rob...@accettura.com
natmaster
would include the new Firefox theme. Is this still the case?
Mike Schroepfer
Mike
Mike Schroepfer
So far there are two bugs we are taking for a Beta1 RC2: 340740 and
337386. If you know of anything else you think should block the beta 1
release please join us tomorrow 10am PDT at #bonecho or 866-216-2181.
Best,
Schrep