601108 - haven't been taking l10n changes for releases done on pm02 since june

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[[e-mail] (:bhearsum)]

In June, we moved the buildbot-configs checkout we use for the releases master from /builds/buildbot/configs to /builds/buildbot/configs-default. However, not all symlinks in the master directory were updated. Specifically, these are all still pointing at the old directory, which is not updated before we do a release:
lrwxrwxrwx 1 cltbld cltbld        35 Aug 11  2009 l10nbuilds2.ini -> ../configs/mozilla2/l10nbuilds2.ini
lrwxrwxrwx 1 cltbld cltbld        35 Aug  7  2009 l10n-changesets -> ../configs/mozilla2/l10n-changesets
lrwxrwxrwx 1 cltbld cltbld        51 Dec 16  2009 l10n-changesets_mobile-1.0.json -> ../configs/mozilla2/l10n-changesets_mobile-1.0.json
lrwxrwxrwx 1 cltbld cltbld        51 Apr  7 18:01 l10n-changesets_mobile-1.1.json -> ../configs/mozilla2/l10n-changesets_mobile-1.1.json
lrwxrwxrwx 1 cltbld cltbld        59 Aug 23 10:48 l10n-changesets_mobile-2.0.json -> ../configs-default/mozilla2/l10n-changesets_mobile-2.0.json
lrwxrwxrwx 1 cltbld cltbld        49 Oct 14  2009 l10n-changesets_mozilla-1.9.2 -> ../configs/mozilla2/l10n-changesets_mozilla-1.9.2

Comment 1

[[e-mail] (:bhearsum)]

These are now fixed.

Comment 2

[[e-mail] (:bhearsum)]

For completeness, a list of potentially affected releases:
- 3.5.14
- 3.5.10
- 3.6.4build7
- 3.5.11
- 3.5.12
- 3.5.13

So we seem to have gotten lucky in a way having not done any Betas here.

Comment 3

[Axel Hecht [:Pike]]

I have a hard time verifying this based on the tags on the 1.9.1 repo, though.

http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/graph and http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/eo/graph so show differently tagged revisions in sync with what https://l10n-stage-sj.mozilla.org/shipping/app/locale-changes/fx3.5 says that we took.

Comment 4

[[e-mail] (:bhearsum)]

It's possible that we were lucky and that the checkout we were looking for l10n-changesets in *was* updated before starting the release, so I'm not too surprised if some are OK. I know this wasn't the case for 3.5.14 though. Take bn-IN:
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/bn-IN

We tagged f1653cf6cf20 for 3.5.14, but l10n-changesets was updated before this release started, and we should've tagged 9d7f833b671b.