No description provided.
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Aki, can you give more details on the l10n impact for the 63 release? Did we build rc1 with the intended strings for l10n? (CCing flod)
The deadline for sign-offs was a week ago (Oct 10). How long has this been broken? RC doesn't seem to be available in product-details, the latest is b14 https://product-details.mozilla.org/1.0/l10n/Firefox-63.0b14-build1.json I did a spot check https://l10n.mozilla.org/shipping/l10n-changesets?av=fx63 Romanian Expected sign-off: 20b5b931be58 (2018-10-10) Product-details: 591f9053c91e (2018-09-24) German Expected sign-off: 72612c2ff687 (018-10-10) Product-details: 2733c3ea372e (2018-09-24) Italian Expected sign-off: 8a24d4f6d59c (2018-09-29) Product-details: aa3f927c589b (2018-09-24) So I assume we're shipping obsolete strings in RC.
(In reply to Francesco Lodolo [:flod] from comment #3) > The deadline for sign-offs was a week ago (Oct 10). How long has this been > broken? We're missing 2 weeks of localization, which is definitely not OK. https://hg.mozilla.org/releases/mozilla-release/log/tip/browser/locales/l10n-changesets.json I've checked build1 and German's preferences are half-translated.
Rok, Aki, how can we make sure that https://hg.mozilla.org/releases/mozilla-release/log/tip/browser/locales/l10n-changesets.json is manually updated with the right revisions for l10n for the next RC and 63 release? Was a follow up bug filed or an item added to your release warrior checklist? Do you need l10n-drivers/relman to file one?
Can we manually run the bumper on mozilla-release?
(In reply to Ryan VanderMeulen [:RyanVM] from comment #6) > Can we manually run the bumper on mozilla-release? I think you should be able to manually land the version currently in beta https://hg.mozilla.org/releases/mozilla-beta/file/2d819200b10b/browser/locales/l10n-changesets.json
Thanks, double check the changesets with l10n.mozilla.org and it looks good.
9 months ago
Severity: normal → major
You need to log in before you can comment on or make changes to this bug.