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

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

116 bytes added , 18 February 2014

Confirmed users

4,293

edits

@@ Line 69: / Line 69: @@
 == Paperwork ==
-Unlike in the past, no per release bugs should be filed anymore. Build notes are also not required, unless something goes wrong. If something does go wrong you must:
+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.
-* Create build notes, and take notes on what went wrong + the fix (no different than before).
+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
 * File a bug on the specific issue you hit. (Eg: "updates failed for 23.0b5")