[FYI] Firefox 4 Beta 8, Mobile Beta 3 in build

Axel Hecht

unread,

Dec 14, 2010, 9:00:34 PM12/14/10

to

Hi,

for your information, the Firefox 4 Betas for Desktop (8) and Mobile (3)
are now in build.

Axel

Axel Hecht

unread,

Dec 15, 2010, 12:10:53 PM12/15/10

to

There was a regression in the release automation, quite a few of those
builds will not work. We'll need to respin basically all of them.

https://bugzilla.mozilla.org/show_bug.cgi?id=619258

Axel

Axel Hecht

unread,

Dec 16, 2010, 10:55:25 AM12/16/10

to

We did a respin, but there seems to be one more,
https://bugzilla.mozilla.org/show_bug.cgi?id=619664.

Axel

Benoit

unread,

Dec 17, 2010, 8:27:02 AM12/17/10

to

Hi Axel,

If we are doing l10n-merge anyway, is it at least possible to take the
latest changesets? I currently see 14 locales with pending signoffs on
https://l10n-stage-sj.mozilla.org/shipping/dashboard?av=fx4.0 (up from
10 yesterday)

<rant>
I have to say this situation is getting quite ridiculous. We do
everything we can to stay in sync with the trunk, and now we seem to be
locked on a two-weeks-old changeset. That means the quality of this beta
is going to be far worse than the previous one where everything was
translated.

We are also going to get lots of pointless bug reports for untranslated
strings although they are ready in the VCS for weeks.

It may be too late for this release already, but please keep this in
mind for the future.

And IMHO, if there is no l10n freeze anymore, the whole idea of signing
off a changeset doesn't make any sense either.
</rant>

--
Benoit
FrenchMozilla l10n team

Axel Hecht

unread,

Dec 17, 2010, 12:15:40 PM12/17/10

to

On 17.12.10 05:27, Benoit wrote:
> Hi Axel,
>
> If we are doing l10n-merge anyway, is it at least possible to take the
> latest changesets? I currently see 14 locales with pending signoffs on
> https://l10n-stage-sj.mozilla.org/shipping/dashboard?av=fx4.0 (up from
> 10 yesterday)
>
> <rant>
> I have to say this situation is getting quite ridiculous. We do
> everything we can to stay in sync with the trunk, and now we seem to be
> locked on a two-weeks-old changeset. That means the quality of this beta
> is going to be far worse than the previous one where everything was
> translated.
>
> We are also going to get lots of pointless bug reports for untranslated
> strings although they are ready in the VCS for weeks.
>
> It may be too late for this release already, but please keep this in
> mind for the future.
>
> And IMHO, if there is no l10n freeze anymore, the whole idea of signing
> off a changeset doesn't make any sense either.
> </rant>
>

Hi Benoit and others,

I do share your concerns about this one, it's not happy-making. I come
to different conclusions, though.

The latest changeset might not be OK to ship. l10n-merge is able to fix
up some things, but not things like, say, horribly broken prefs, totally
unusable search, not building at all (see search) etc.

I have thought about taking new sign-offs for the respins, but quite
honestly, this beta iteration was broken so badly, I just didn't want to
add more parameters to it.

I'm thinking about ways to enhance the dashboard infrastructure to
actually expose the difference between what's shipping and what's there
in a meaningful way. That'd allow us to make informed decisions and
outreach.

There's also a lot of talking this week about how to actually ship on
schedule, which would hopefully fix things like string freeze again.

That said, I really hope that this was the last beta with "oh, we gotta
do X here", like b6/7 (feature freeze) and b8 (sync). Reading what I
type, that looks silly. Anyway, let's keep our fingers crossed that we
get back to a quicker cadence of betas than the last few.

Axel