810394 - figure out how to deal with final release / esr l10n changesets in release kickoff

Status: RESOLVED FIXED

(Release Engineering :: Release Automation, defect)

Description

[[e-mail] (:bhearsum)]

Both of these releases have different challenges when it comes to l10n. For final releases, we don't have accurate l10n milestones on the dashboard. If we can't get that fixed, we may need to point release runner at a different location than the l10n dashboard -- perhaps an edited copy on a people account or some such thing. Maybe give it the changesets file directly instead of a URL.

For ESRs, we don't have l10n milestones at all because we don't take l10n changesets. For these we can probably just point release runner at the currently checked in l10n changesets, eg: https://hg.mozilla.org/build/buildbot-configs/raw-file/FIREFOX_10_0_10esr_RELEASE/mozilla/l10n-changesets_mozilla-esr10

Comment 1

[[e-mail] (:bhearsum)]

A few of us talked about this in a meeting today and came to the conclusion that feeding in a changesets file directly isn't such a bad idea. Doing that would put the informational directly into the system (rather than getting it indirectly), and allow us to edit the incorrect dashboard one without needing to put it on people or some other server.

If we do this, I want to make sure the file is reviewable on releases.html, so whomever it is that's marking the releases as ready can make sure the correct locales are removed before marking as ready.

Comment 3

[[e-mail] (:bhearsum)]

This is fixed in the latest version of kickoff.