Release:Release Automation on Mercurial:Starting a Release: Difference between revisions

Release:Release Automation on Mercurial:Starting a Release (view source)

832 bytes removed , 11 February 2013

canmove, Confirmed users

6,439

edits

@@ Line 54: / Line 54: @@
 * Firefox releases (that is, a release on the release channel) need partial updates from the 3 past versions with the most users. If you don't know how to get this information ask someone in RelEng or RelMan.
 * A "go" for Firefox implies a "go" for Fennec, too
-= Run Release Runner =
-After your release has been submitted and reviewed you need to run release runner, which will create the patches, run release sanity, reconfig, and start the release. Release runner runs in the background on buildbot-master36 and will e-mail release@mozilla.com upon failure. As it works through its operations it will update [https://ship-it-dev.allizom.org/releases.html Ship It's list of releases] with details and rough error messages.
-If you hit any errors that you don't know how to debug on your own, ask someone for help.
-If you have any failures after configs or tags have been pushed you won't be able to restart release runner without commenting out some sections of it. If you don't know how to do this, ask for help.
-Once {{bug|810393}} is fixed, this will happen without manual intervention.