Confirmed users
4,293
edits
Release:Release Automation on Mercurial:Starting a Release: Difference between revisions
Jump to navigation
Jump to search
Release:Release Automation on Mercurial:Starting a Release (view source)
Revision as of 21:35, 18 February 2014
, 18 February 2014Note some sections as RelMan tasks
(Note some sections as RelMan tasks) |
|||
| Line 4: | Line 4: | ||
= L10N Changesets = | = L10N Changesets = | ||
<b>''This task is completed by Release Management''</b> | |||
Currently we have separate changesets files for Fennec and Firefox. Both are generated from the [https://l10n.mozilla.org/shipping/milestones l10n dashboard]<br /> | Currently we have separate changesets files for Fennec and Firefox. Both are generated from the [https://l10n.mozilla.org/shipping/milestones l10n dashboard]<br /> | ||
If you need changesets for a subsequent build (eg. beta1 build #2), copy them from the previous ship-it request.<br /> | If you need changesets for a subsequent build (eg. beta1 build #2), copy them from the previous ship-it request.<br /> | ||
| Line 50: | Line 52: | ||
= Submit to Ship It = | = Submit to Ship It = | ||
<b>''This task is completed by Release Management''</b> | |||
Releases are initiated through the [https://ship-it.mozilla.org/ Ship It webapp]. When you're ready to start a release, you can use the [https://ship-it.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-it.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-it.mozilla.org/ Ship It webapp]. When you're ready to start a release, you can use the [https://ship-it.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-it.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. | ||
| Line 68: | Line 72: | ||
* L10n changesets match the same format as the previous release and roughly the same number of entries | * L10n changesets match the same format as the previous release and roughly the same number of entries | ||
= Paperwork = | |||
A release specific bug should be filed, except for b2 to bN (end of cycle). Rail is on the hook to pre-file these (and also assign releases to people), but it should be done manually for chemspills. | A release specific bug should be filed, except for b2 to bN (end of cycle). Rail Aliiev is on the hook to pre-file these (and also assign releases to people), but it should be done manually for chemspills. | ||
For b2 to bN, build notes are not required, unless something goes wrong. If something does go wrong you must: | For b2 to bN, build notes are not required, unless something goes wrong. If something does go wrong you must: | ||
* Create build notes, and take notes on what went wrong + the fix | * Create build notes, and take notes on what went wrong + the fix | ||
* File a bug on the specific issue you hit. (Eg: "updates failed for 23.0b5") | * File a bug on the specific issue you hit. (Eg: "updates failed for 23.0b5") | ||