Closed Bug 1430044 Opened 7 years ago Closed 7 years ago

state of l10n changesets after central to beta merge

Categories

(Release Engineering :: Release Automation, enhancement)

Product:
Release Engineering
Component:
Release Automation
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(firefox59blocking fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox59 blocking fixed

People

(Reporter: jcristau, Assigned: Callek)

Details

We merged 59 to beta yesterday, and beta will remain closed for 10 days, which means the l10n-bump tasks won't be updating revisions in {browser,mobile}/locales/l10n-changesets.json, and they all stay "default". Is that what we want for DevEd 59.0b[12], or should we have actual revision numbers there?
+pike to confirm. I think we want revision numbers there (i.e. sign-offs). We can live with 'default', but any error landing in m-c would also make it to the devedition build.
Yeah, I'd feel better if we had signed-off revisions. I'd be fine with a static one, though, and I checked with flod on irc, he's, too.
Ben, do you know if we can just update the l10n revisions in ship-it to the ones from https://l10n.mozilla.org/shipping/l10n-changesets?av=fx59 before starting the 59.0b1 release, or if something uses the in-tree l10n-changesets.json file and that should also be updated?
Flags: needinfo?(bhearsum)
I commented in IRC. We can't just trigger a gecko 59 build and expect ship-its l10n to be used, source of truth now is in-tree. Ship-it's l10n is only used for mozilla.org needs (via product-details). After :jlorenzo's work elsewhere this is now automatically pulled from in-tree. I found in history on bm01: `python2.7 mozharness/scripts/l10n_bumper.py -c mozharness/configs/l10n_bumper/mozilla-beta.py --ignore-closed-tree` which I am running now to try and do the bump for us.
Flags: needinfo?(bhearsum)
Callek ran the l10n bumper manually, and dustin forced a decision task despite DONTBUILD, so we should be good for 59 now. Hopefully next time around we remember this needs to be done as part of the merge. https://hg.mozilla.org/releases/mozilla-beta/rev/e29dbd18139ddd186f05e3de1df2c3a99cdeaf6b https://hg.mozilla.org/releases/mozilla-beta/rev/ea3f0010577337c203fad06be318727bf039c536
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox59: --- → fixed
tracking-firefox59: --- → blocking
Resolution: --- → FIXED
Assignee: nobody → bugspam.Callek
You need to log in before you can comment on or make changes to this bug.