449202 - Get Thunderbird L10N builds working on comm-central

Status: RESOLVED FIXED

(Thunderbird :: Build Config, defect, P1)

Description

[Mark Banner (:standard8)]

Bug 434289 is working on setting up L10N builds for mozilla-central. I'm going to track the work that we need to do on Thunderbird here.

Some of this will be tracking what Robert is doing for SeaMonkey in bug 446119.

Comment 1

[Mark Banner (:standard8)]

Attachment: [checked in] Fix paths in mail/locales/Makefile.in

This patch does what Robert did for SM in bug 446119 - corrects some paths in the locales Makefile.in so that "make langpack-ab-CD" (with other appropriate set up) will work correctly in comm-central.

Comment 2

[Axel Hecht [:Pike]]

Comment on attachment 332685 [details] [diff] [review]
[checked in] Fix paths in mail/locales/Makefile.in

Looks good to me, fwiw.

Comment 3

[Mark Banner (:standard8)]

As we are releasing l10n builds with alpha 2, we definitely need to be able to do so again with beta 1.

Comment 4

[Mark Banner (:standard8)]

Comment on attachment 332685 [details] [diff] [review]
[checked in] Fix paths in mail/locales/Makefile.in

Checked in, changeset id: 81:2e80f8bdd1cc

Comment 5

[David Ascher (:davida)]

Switching for b1 flags to target milestones, to avoid flag churn.

Comment 7

[Philippe M. Chiasson (:gozer)]

Got the first successful l10n build up on ftp.mozilla.org : http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/thunderbird-3.0b1pre.ga-IE.win32.installer.exe

More should trickle in as l10n repos are changing, and the real churn will be tonight, after the nightlies. I'll wait and see how that goes.

Comment 8

[Mark Banner (:standard8)]

So we've had some more popup overnight. What I've just realised is that they are going into:

ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-comm-central/

and not:

ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-trunk-l10n/

which was the original location, is there any way we could fix that? There we're keeping things in the same structure.

Comment 9

[Robert Kaiser]

latest-trunk* should not be used any more for uploading, but it should be easy to make it latest-comm-central-l10n and symlink latest-trunk-l10n to it (AFAIK, this is what FF does).
gozer, this would mean changing self.mainBranch to self.localesBranch in the MozillaStageUpload step of mozl10n.py.

I did make the upload fo to latest-comm-central as SeaMonkey always had them in latest-trunk and I don't really know why L10n files should be treated so differently and go into a separate directory when they are equal in what code the contain and are equal in releases. I think though that whatever way we go, we should be consistent at least between SeaMonkey and Thunderbird as to how we treat that.

Comment 10

[Philippe M. Chiasson (:gozer)]

I've moved latest-trunk-l10n content to the newly created latest-comm-central-l10n directory, and made the suggested symlink

Comment 11

[Philippe M. Chiasson (:gozer)]

Changed where the l10n builds are uploaded, as suggested in comment #9

changeset:   290:36e699d20f74
tag:         tip
user:        Philippe M. Chiasson <[e-mail]>
date:        Fri Sep 05 12:03:55 2008 -0400
summary:     Bug 449202. Upload l10n builds to comm-central-l10n/

Comment 12

[Philippe M. Chiasson (:gozer)]

We have now localized builds in quite a few locales:
de
en-GB
en-US
es-AR
es-ES
fr
ga-IE
it
lt
sk

The other ones are failing because they have not yet adjusted to the change in bug 450257.

Apart from that, it's now working as expected.