Confirmed users
4,293
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 20:44, 28 October 2014
, 28 October 2014→Paperwork: make app agnostic
(→Paperwork: Process changes for notes and checklist) |
(→Paperwork: make app agnostic) |
||
| Line 80: | Line 80: | ||
A release specific bug should be filed, except for b2 to bN (end of cycle). releaseduty is on the hook to pre-file these, but it should be done manually for chemspills. | A release specific bug should be filed, except for b2 to bN (end of cycle). releaseduty is on the hook to pre-file these, but it should be done manually for chemspills. | ||
Build notes are required for every release, located at Releases/ | Build notes are required for every release, located at Releases/<app>_<version>/BuildNotes (eg [[Releases/Firefox_34.0b4/BuildNotes]], [[Releases/Firefox_33.0.2/BuildNotes]], [[Releases/Thunderbird_31.2.0/BuildNotes]]). A copy of the [[Releases/RelEngChecklist | Checklist]] should be copied in, so that work items can be marked off as they are completed. This makes handing-off releases between people more reliable. | ||
File bugs on specific issues you hit which can be fixed by automation improvements, or for patches that require review and there is no release tracking bug. | File bugs on specific issues you hit which can be fixed by automation improvements, or for patches that require review and there is no release tracking bug. | ||
[[category:Release_Management|R]] | [[category:Release_Management|R]] | ||