Howdy Everyone,
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.
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)
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 well 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. Well start approving and landing them once the tree is clear
from beta1.
Well 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 todays status meeting:
in case you want more details.
dev-planning mailing list
dev-planning (AT) lists (DOT) mozilla.org

To add to this, we intend to pull the l10n repository for Firefox 2.0
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 K for B1.

Mike Schroepfer wrote:
Howdy Everyone,

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.

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)

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 well 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. Well start approving and landing them once the tree is clear
from beta1.

Well 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 todays status meeting:

in case you want more details.

dev-planning mailing list
dev-planning (AT) lists (DOT) mozilla.org

Just curious, I had seen posted on other Mozilla sources that beta 1
would include the new Firefox theme. Is this still the case?

Mike Schroepfer wrote:
Howdy Everyone,

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.

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)

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:

in case you want more details.

dev-planning mailing list
dev-planning (AT) lists (DOT) mozilla.org

No - Beta1 does not include any theme changes.

Mike

natmaster wrote:
Just curious, I had seen posted on other Mozilla sources that beta 1
would include the new Firefox theme. Is this still the case?

Mike Schroepfer wrote:
>Howdy Everyone,
>>
>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.
>>
>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)
>>
>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:
>>
>
>>
>in case you want more details.

dev-planning mailing list
dev-planning (AT) lists (DOT) mozilla.org

Howdy,

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

Mike Schroepfer wrote:
Howdy Everyone,

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.

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)

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 well 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. Well start approving and landing them once the tree is clear
from beta1.

Well 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 todays status meeting:

in case you want more details.

dev-planning mailing list
dev-planning (AT) lists (DOT) mozilla.org