canmove, Confirmed users
6,439
edits
Release:Release Automation on Mercurial:Starting a Release: Difference between revisions
Release:Release Automation on Mercurial:Starting a Release (view source)
Revision as of 19:17, 6 March 2013
, 6 March 2013→Submit to Ship It
m (→Submit to Ship It: fix typo) |
|||
| Line 49: | Line 49: | ||
= Submit to Ship It = | = Submit to Ship It = | ||
Releases are initiated through the [https://ship.mozilla.org/ Ship It webapp]. When you're ready to start a release, you can use the [https://ship.mozilla.org/submit_release.html "Submit a new release" page] to submit it. Once it's in the system you should find '''someone else''' to review it for you. They can see it and mark it as ready on [https://ship.mozilla.org/releases.html the "View releases" page]. If multiple releases are expected around the same time it's often best to wait until all are ready for review, so that they can be started at the same time. | Releases are initiated through the [https://ship.mozilla.org/ Ship It webapp]. When you're ready to start a release, you can use the [https://ship.mozilla.org/submit_release.html "Submit a new release" page] to submit it. Once it's in the system you should find '''someone else''' to review it for you. They can see it and mark it as ready on [https://ship.mozilla.org/releases.html the "View releases" page]. If multiple releases are expected around the same time it's often best to wait until all are ready for review, so that they can be started at the same time. | ||
Track Ship-It status on the [https://ship.mozilla.org/releases.html the "View releases" page]. If there are errors reported, check your email for details from "<tt>cltbld</tt>" with subject starting "<tt>[release-runner]</tt>". | Track Ship-It status on the [https://ship.mozilla.org/releases.html the "View releases" page]. If there are errors reported, check your email for details from "<tt>cltbld</tt>" with subject starting "<tt>[release-runner]</tt>". | ||
| Line 61: | Line 57: | ||
* 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. | * 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 | * A "go" for Firefox implies a "go" for Fennec, too | ||
== How to review a release == | |||
Here's a list of things we normally look for when reviewing release submissions: | |||
* Version, build number, branch, and changesets match what was given in the "go" e-mail. | |||
* Relbranch is absent unless specified in the go. | |||
* Partial versions are from recent releases and using the same build number that was shipped for that version. | |||
* Dashboard check is enabled for betas, disabled for release/esr. | |||
* L10n changesets match the same format as the previous release. | |||