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

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

243 bytes added , 28 October 2014

→‎Paperwork: Process changes for notes and checklist

Confirmed users

4,293

edits

@@ Line 78: / Line 78: @@
 = Paperwork =
-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.
+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.
-For b2 to bN, build notes are not required, unless something goes wrong. If something does go wrong you must:
+Build notes are required for every release, located at Releases/Firefox_<version>/BuildNotes (eg [[Releases/Firefox_34.0b4/BuildNotes]], [[Releases/Firefox_33.0.2/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.
-* 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 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]]