523315 - Ensure l10n dashboard is ready for comm-1.9.1 branch

Status: RESOLVED FIXED

(Localization Infrastructure and Tools :: Administration / Setup, task)

Description

[Mark Banner (:standard8)]

Currently the l10n dashboard is pulling the comm-* builds from comm-central.

I think we can now switch sea20x, sunbird10x, tb30x to be pulling from http://hg.mozilla.org/releases/comm-1.9.1/ rather than the trunk comm-central.

(note: until we formally branch, I'm keeping comm-central and comm-1.9.1 in sync, however we can still switch now IMHO, as all apps are in string freeze).

At some stage we'll need to set up new versions in the l10n dashboard, however, I'm going to hold off a little longer on that decision as it doesn't affect branching which is the more important thing this week.

Comment 1

[Axel Hecht [:Pike]]

I need paths to l10n.ini files for those to switch the dashboard over.

I'll need code names for the comm-central setup, too. Something like tb31x or whatever the next major version is most likely to be.

Comment 2

[Mark Banner (:standard8)]

(In reply to comment #1)
> I need paths to l10n.ini files for those to switch the dashboard over.

For TB, I think use this one, because that's what the build automation is using:

http://hg.mozilla.org/releases/comm-1.9.1/file/tip/mail/locales/l10n-1.9.1.ini

For SM + SB these are the only options:

http://hg.mozilla.org/releases/comm-1.9.1/file/tip/suite/locales/l10n.ini
http://hg.mozilla.org/releases/comm-1.9.1/file/tip/calendar/locales/l10n.ini

> I'll need code names for the comm-central setup, too. Something like tb31x or
> whatever the next major version is most likely to be.

Well, that's the bit I was going to delay on. For TB, I guess you can use:

tb31x => http://hg.mozilla.org/comm-central/file/tip/mail/locales/l10n-central.ini

and that will point to 1.9.3 for now (note: we may be coming off of 1.9.2 for 3.1, but we won't know that for a few weeks yet).

For SM and SB, I guess you can do:

sea21x => http://hg.mozilla.org/comm-central/file/tip/suite/locales/l10n.ini
sb11x => http://hg.mozilla.org/comm-central/file/tip/calendar/locales/l10n.ini

Although these will point to mozilla-1.9.1 until after we've branched.

I'm not sure there is intended to be a sb11x release, but maybe it will help locales with translating Lightning strings anyway.

Comment 3

[Axel Hecht [:Pike]]

Attachment: add tb31x, migrate the other comm-central to comm-1.9.1, poll comm-1.9.1

So neither suite not calendar are ready to actually branch, they need l10n.inis. I just migrate those to pull their current comm stuff from comm-1.9.1.

For thunderbird, I added the tree and disambiguated the l10n.inis.

And added a poller to comm-1.9.1 to master.cfg.

I hope this will do it, together with a clobber to make sure that we're not keeping old comm-central clones around.

I hope that client.py --skip-com checkout does the right thing to pull in mozilla-central or 1.9.1, as that's what's used for the factory.

Comment 4

[Robert Kaiser]

Attachment: Adjust l10n.ini for SeaMonkey trunk

Here's a patch for adjusting the l10n.ini for SeaMonkey trunk (comm-central), with that change, we should be able to add a sea21x as well, pointing to that ini.

Comment 5

[Robert Kaiser]

Attachment: adjust SeaMonkey l10n.ini for comm-1.9.1

And actually, while looking into that stuff, I found that reporter on comm-1.9.1 pointed to mozilla-central instead of 1.9.1, this patch should correct that as well (good that reporter doesn't change a lot).

Comment 6

[Robert Kaiser]

OK, the SeaMonkey patches are in, we should be ready for making a sea21x available on dashboard :)

Comment 7

[Axel Hecht [:Pike]]

which seamonkey tree names should pick up which l10n.ini's?

Comment 8

[Robert Kaiser]

sea20x => http://hg.mozilla.org/releases/comm-1.9.1/file/default/suite/locales/l10n.ini
sea21x => http://hg.mozilla.org/comm-central/file/default/suite/locales/l10n.ini

Comment 9

[Axel Hecht [:Pike]]

This should be all fixed now.

Comment 10

[Axel Hecht [:Pike]]

tools tsunami, sorry.