Closed Bug 826825 Opened 12 years ago Closed 12 years ago

Remove mn, sw during beta-release migration for Firefox 18

Categories

(Release Engineering :: Release Requests, defect)

Product:
Release Engineering
Component:
Release Requests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox18+ fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox18 + fixed

People

(Reporter: akeybl, Assigned: akeybl)

References

Details

Cloning for FF18 +++ This bug was initially created as a clone of Bug #811788 +++ We're keeping mn and sw in beta for Firefox 17, please remove those from l10n-changesets and shipped-locales.
This is normally filed by Axel. We should post-mortem why this was missed for FF18.
tracking-firefox18: --- → +
From the previous bug "That just leaves l10n-changesets when rail and I land them manually in buildbot-configs."
(In reply to Alex Keybl [:akeybl] from comment #1) > This is normally filed by Axel. We should post-mortem why this was missed > for FF18. https://bugzilla.mozilla.org/show_bug.cgi?id=811054 would help us not forget this IMO. If the process was always "grab (accurate) files from dashboard", we'd never need to remember to remove locales.
https://hg.mozilla.org/releases/mozilla-release/rev/650ead2dacc4
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Sorry for the trouble. As for why, the reasons are likely a mix of: - it's manual work that nobody but me does - holidays - I've been sucked into gaia v1, stepping in for stas, and neglected much of desktop all around this cycle. We're having a bunch of locales in not-as-good-as-possible shape in 18, see also https://groups.google.com/forum/#!topic/mozilla.dev.l10n/cd_7YbPZlfk One thing I notice after the fact is that the "l10n freeze for release" was the regular beta counted from the start of the cycle, not from the end of the cycle? Anyway, I kinda paged out the desktop release during christmas, as I wouldn't take changes to it no more, and did so more agressively than what was healthy.
(In reply to Axel Hecht [:Pike] from comment #5) > Sorry for the trouble. > > As for why, the reasons are likely a mix of: > > - it's manual work that nobody but me does Which is why the dashboard should be serving correct contents - then nobody has to remember to do it.
status-firefox18: --- → fixed
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.