Mobile/Releases/Release Checklist: Difference between revisions

Mobile/Releases/Release Checklist (view source)

227 bytes removed , 25 February 2010

Confirmed users

6,300

edits

@@ Line 21: / Line 21: @@
 * Decision on release date and features - <strong>Entire team</strong>
 ** Update [[Releases]] page - <font color="blue">Project lead</font>
-** Decide urgency of release and what type of beta
-*** more urgent releases with fewer changes typically get shorter betas
-** File bug mozilla.org:RelEng - <font color="green">Project lead / RelEng lead</font>
-*** specifies product name, branches and approx date if known
-*** explicitly state if there are partner repacks; depending on case, this may end up being tracked in separate bug with different people.
-** if there are any changes needed in metrics, file bug in mozilla.org:MozillaStats and link to RelEng bug.
 ** Update Releases/PRODUCT&VERSION with proposed schedule - <font color="blue">Project lead</font>
 ** Email mobile@mo with proposed schedule - <font color="blue">Project lead</font>
 ** Email AMO with version number for addon compatibility - <font color="blue">Project lead</font>
 ** Email SUMO with feature list for the release - <font color="blue">Project lead</font>
+** File bug mozilla.org:RelEng - <font color="green">RelEng lead</font>
+*** specifies product name, branches and approx date if known
+*** explicitly state if there are partner repacks
+** if there are any changes needed in metrics, file bug in mozilla.org:MozillaStats and link to RelEng bug.
 * Triage of blocking/approval requests as needed - <strong>Entire team (minus build)</strong>