Confirmed users
1,351
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 22:03, 18 August 2015
, 18 August 2015add link to build notes index
(relman needs to be cc'd) |
(add link to build notes index) |
||
| Line 82: | Line 82: | ||
* ensure the relman lead is cc'd (since they start the build, and need to be aware of any infrastructure blockers) | * ensure the relman lead is cc'd (since they start the build, and need to be aware of any infrastructure blockers) | ||
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. | [[Releases/BuildNotesIndex|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]] | ||