Firefox, Mobile, SeaMonkey, Thunderbird - branches, versions, Aurora

[Siarhei]

Hi all,

Unfortunately I could track the changes of localization process last time.

I lost myself in all these changes.

L10n Dashboard doesn't help to figure out which branches are used for building.

It shows that:

- fx40x is built from mozilla-central, localization is taken from l10n-central
https://l10n-stage-sj.mozilla.org/builds/builders/compare/121667
- fx_aurora is built from mozilla-aurora, localization is taken from releases/l10n/mozilla-aurora
https://l10n-stage-sj.mozilla.org/builds/builders/compare/127078
- fx_central is built from mozilla-central, localization is taken from l10n-central
https://l10n-stage-sj.mozilla.org/builds/builders/compare/128558

There is no difference for fx40x and fx_central, but the dashboard shows different results for them.

Is there any list of code branches and l10n branches used to build products?

With best regards,

Siarhei

[flod]

Il 24/04/11 11.50, Siarhei ha scritto:

> - fx40x is built from mozilla-central, localization is taken from
> l10n-central
> https://l10n-stage-sj.mozilla.org/builds/builders/compare/121667

This is wrong: fx40x it's built from *releases/mozilla-2.0*, locales
taken from *releases/l10n-mozilla-2.0* (that build log is over a month
old).
That's why you see differences between fx_central and fx40x.

Francesco

[Siarhei]

На 04/24/2011 01:20 PM, flod напісаў(ла):

That is why I ask if there is any source that tells us which branches should be used for localization.

https://wiki.mozilla.org/L10n doesn't provide any information about branches, L10n Dashboard shows wrong branches.

With best regards,

Siarhei

[Axel Hecht]

No, there's no such list, a long standing (and non-trivial) bug on the
dashboard.

For the next release to be shipped to end-users, you want to work on the
aurora branch.

You've got 'til around May 13 to work on the strings before we make them
become beta, and get the next round of strings onto aurora.

See
http://blog.mozilla.com/axel/2011/04/11/being-a-localizer-in-the-rapid-release-cycle/
for an outline (the repo names changed a bit since I blogged that).

Axel

[smo]

> Seehttp://blog.mozilla.com/axel/2011/04/11/being-a-localizer-in-the-rapi...

> for an outline (the repo names changed a bit since I blogged that).
>
> Axel

Just a reminder, Axel: the thread started as "Firefox, Mobile,
SeaMonkey, Thunderbird".
Beside the Snow White Fx there's a few dwarves standing around,
pining for somebody's
attention.

Regards

smo

[Justin Wood (Callek)]

Firefox 4.0: releases/mozilla-2.0, releases/l10n-mozilla-2.0/*
SeaMonkey 2.1: releases/comm-2.0, releases/l10n-mozilla-2.0/*
SeaMonkey 2.2+: comm-central, mozilla-central, l10n-central (for now,
future unclear)
Thunderbird 3.3: comm-central, mozilla-aurora (for now),
releases/l10n/mozilla-aurora
Thunderbird 3.4+: comm-central, mozilla-central, l10n-central.

So Summary:

See
http://blog.mozilla.com/axel/2011/04/11/being-a-localizer-in-the-rapid-release-cycle/
for Firefox.

Think about that one as well, as it relates to Thunderbird (but I'm
unsure the exact details on if they are freezing l10n at the same time,
but it is at least a start).

For SeaMonkey2.1, which will come really soon now, you'll want to update
|suite/| in your l10n-mozilla-2.0 repo.

I agree a nice wiki page or something would be best for this stuff, with
"en-US Freeze/frozen" listing for each product, link(s) to l10n-policy
or some such -- per product. And identification of repo's to use. and/or
other helpful links.

--
~Justin Wood (Callek)

[Siarhei]

Justin, thank you.

The things are more clear now.

With best regards,

Siarhei

На 04/28/2011 07:19 AM, Justin Wood (Callek) напісаў(ла):