Closed Bug 523315 Opened 10 years ago Closed 10 years ago

Ensure l10n dashboard is ready for comm-1.9.1 branch

Categories

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

task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Assigned: Pike)

References

Details

(Keywords: fixed-seamonkey2.0.1)

Attachments

(3 files)

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.
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.
(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.
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.
Assignee: nobody → l10n
Status: NEW → ASSIGNED
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.
Attachment #407986 - Flags: review?(l10n)
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).
Attachment #407987 - Flags: review?(l10n)
Attachment #407987 - Flags: approval-seamonkey2.0.1?
Attachment #407987 - Flags: approval-seamonkey2.0.1? → approval-seamonkey2.0.1+
Attachment #407986 - Flags: review?(l10n) → review+
Attachment #407987 - Flags: review?(l10n) → review+
OK, the SeaMonkey patches are in, we should be ready for making a sea21x available on dashboard :)
which seamonkey tree names should pick up which l10n.ini's?
This should be all fixed now.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
tools tsunami, sorry.
Component: Infrastructure → Administration / Setup
Flags: approval-seamonkey2.0.1+
Product: Mozilla Localizations → Localization Infrastructure and Tools
You need to log in before you can comment on or make changes to this bug.