Initially it would probably only be for informational purposes, but it could be used for things like: * Data gathering about how many urgent releases have done in N period. * Sending e-mail out to release-drivers/release/infra/etc. to warn
The work involved here is very similar to bugs 823841 and 812322. This commit could be used as a rough guide to doing this: http://git.mozilla.org/?p=build/release-kickoff.git;a=commitdiff;h=9c6a969d3a8a4f19aa0009593a6660d3b3c422bf
Rail and I just talked about this and we're wondering if urgent/not urgent is going to be enough, or whether we need a something more finer grained. Also, do chemspills need to be distinguished explicitly, or only by their priority?
(In reply to Ben Hearsum [:bhearsum] from comment #2) > Rail and I just talked about this and we're wondering if urgent/not urgent > is going to be enough, or whether we need a something more finer grained. It would match what we currently use, at least. > Also, do chemspills need to be distinguished explicitly, or only by their > priority? Urgent builds are typically only used for chemspills, in support of chemspills (quick turnaround beta), or to hit a specific partner timeline.
Mass component change for ship it bugs.
Let's WONTFIX it. We have an ability to mark releases as "security driven". Not sure if adding extra logic to send more emails is something we are going to touch anytime soon. KISS FTW!