Releases/Firefox 3.6.4/Checklist: Difference between revisions

Update release checklist
(First crack at release checklist, will clean up in a bit)
 
(Update release checklist)
Line 1: Line 1:
== Setup/Project Definition ==
* <del>Meet and schedule release - <strong>Entire team</strong> </del> '''<font color="green">[DONE]</font>'''
* <del>Meet and schedule release - <strong>Entire team</strong> </del> '''<font color="green">[DONE]</font>'''


* <del>Decision on release date - <strong>Entire team</strong></del> '''<font color="green">[DONE]</font>'''
* <del>Decision on release date - <strong>Entire team</strong></del> '''<font color="green">[DONE]</font>'''
** <del>Update [[Releases]] page - <font color="blue">Project lead</font></del> '''<font color="green">[DONE]</font>'''
** <del>Update [[Releases]] page - <font color="blue">Project lead</font></del>
** <del>Update Releases/PRODUCT&VERSION with proposed schedule - <font color="blue">Project lead</font></del> '''<font color="green">[DONE]</font>'''
** <del>Update Releases/PRODUCT&VERSION with proposed schedule - <font color="blue">Project lead</font></del>
** <del>Email dev-planning and release-drivers with proposed schedule - <font color="blue">Project lead</font></del> '''<font color="green">[DONE]</font>'''
** <del>Email dev-planning and release-drivers with proposed schedule - <font color="blue">Project lead</font></del>


* Triage of blocking/approval requests as needed - <strong>Entire team (minus build)</strong>
* Triage of blocking/approval requests as needed - <strong>Entire team (minus build)</strong> '''<font color="blue">[ONGOING]</font>'''
** Schedule meetings - <font color="blue">Project lead</font>
** Schedule meetings - <font color="blue">Project lead</font>
** Alert developers of blockers - <font color="blue">Project lead</font>
** Alert developers of blockers - <font color="blue">Project lead</font>
** Alert developers of upcoming freeze - <font color="blue">Project lead</font>
** Alert developers of upcoming freeze - <font color="blue">Project lead</font>


* Development code freeze, Build 1 - <font color="red">Dev lead</font>
== Build 1 ==
 
* <del>Development code freeze, Build 1 - <font color="red">Dev lead</font></del> '''<font color="green">[DONE]</font>'''
** <del>Hand off to QA for verifications - <font color="orange">QA Lead</font></del>
 
* <del>Ready for builds</del> '''<font color="green">[DONE]</font>'''
** <del>Email release-drivers when all code is in with formal "Go" - <font color="blue">Project lead</font></del>
*** <del>For 1.9.0, include timestamp and bonsai URI down to the last checkin. Specify timezone in email as well (PST vs PDT).</del>
*** <del>For 1.9.1, include a changeset</del>
*** <del>Specify l10n cut off (1.9.0-only) as well</del>
 
* <del>Builds created (all locales) - <font color="green">Build lead</font></del> '''<font color="green">[DONE]</font>'''
** <del>Email release-drivers when builds are created - <font color="green">Build lead</font></del>
 
* <del>QA tests builds - <font color="orange">QA Lead</font></del> '''<font color="green">[DONE]</font>'''
** <del>QA completes testing and maps it onto their test plan page (usually at Releases/PRODUCTNAME_VERSION/Test_Plan on the wiki) - <font color="orange">QA Lead</font></del>
** <del>When signed off, email release-drivers with notification - <font color="orange">QA Lead</font></del>
 
* <del>Build snippets on betatest channel - <font color="green">Build lead</font></del> '''<font color="green">[DONE]</font>'''
** <del>Email QA lead when finished - <font color="green">Build lead</font></del>
 
* <del>Project lead creates [[Webtools:Release_Notes|beta release notes]]; staging and live - <font color="blue">Project Lead</font></del> '''<font color="green">[DONE]</font>'''
 
* <del>QA verifies snippets and website and emails release-drivers when signed off - <font color="orange">QA Lead</font></del> '''<font color="green">[DONE]</font>'''
 
* <del>If any of those fail, email release-drivers with a formal "stop" notification and a second "go" notification when the process is started again - <font color="blue">Project Lead</font></del> '''<font color="green">[DONE]</font>'''
 
* <del>"Go" to beta</del> '''<font color="green">[DONE]</font>'''
** <del>Formal "Go" email sent to release-drivers - <font color="blue">Project lead</font></del>
** <del>Build snippets pushed to beta channel - <font color="green">Build lead</font></del>
** <del>QA verifies snippets on beta channel - <font color="orange">QA Lead</font></del>
 
* Beta period '''<font color="blue">[ONGOING]</font>'''
** <del>Announce to release-drivers, m.d.a.<application> (i.e. thunderbird or firefox), m.announce.prerelease, m.d.planning - <font color="blue">Project lead</font></del>
** <del>Notify mirrors of beta release - <font color="blue">Project lead</font> emails infra</del>
** <del>Notify PR (melissa) of "we're shipping in a week" estimate - <font color="blue">Project lead</font></del>
** Announce to [https://intranet.mozilla.org/Firefox:SecurityVendors AV/Firewall vendors] - <font color="blue">Project lead</font>
** Announce to security group - <font color="red">Security lead</font>
*** to security-group and security-announce aliases
** Monitor feedback - <font color="orange">QA Lead</font>, <font color="blue">Project lead</font>
 
== Build 2 ==
 
* Development code freeze, Build 2 - <font color="red">Dev lead</font>
** Hand off to QA for verifications - <font color="orange">QA Lead</font>
** Hand off to QA for verifications - <font color="orange">QA Lead</font>


* Ready for builds
* Ready for builds
** Email release-drivers when all code is in with formal "Go" - <font color="blue">Project lead</font>
** Email release-drivers when all code is in with formal "Go" - <font color="blue">Project lead</font>
*** For 1.9.0, include timestamp and bonsai URI down to the last checkin. Specify timezone in email as well (PST vs PDT).
*** For 1.9.1, include a changeset
*** For 1.9.1, include a changeset
*** Specify l10n cut off (1.9.0-only) as well


* Builds created (all locales) - <font color="green">Build lead</font>
* Builds created (all locales) - <font color="green">Build lead</font>
Line 66: Line 108:
** Notify PR (melissa@m.c) of "we're shipping in x days/hours/minutes" estimate - <font color="blue">Project lead</font>
** Notify PR (melissa@m.c) of "we're shipping in x days/hours/minutes" estimate - <font color="blue">Project lead</font>


* Final Release
== Final Release ==
** Bits to mirrors - <font color="blue">Project lead</font> sends "go email" at least 8 hours ahead of time
* Bits to mirrors - <font color="blue">Project lead</font> sends "go email" at least 8 hours ahead of time
*** Push actual bits - <font color="green">Build lead</font>
** Push actual bits - <font color="green">Build lead</font>
** Verify bits on releasetest channel - <font color="orange">QA Lead</font>
* Verify bits on releasetest channel - <font color="orange">QA Lead</font>
** Push website changes - <font color="blue">Project lead</font>
* Push website changes - <font color="blue">Project lead</font>
** Push security advisories - <font color="red">Security lead</font>
* Push security advisories - <font color="red">Security lead</font>
** QA verifies website changes - <font color="orange">QA Lead</font>
* QA verifies website changes - <font color="orange">QA Lead</font>
** Build pushes to release channel - <font color="green">Build lead</font>
* Build pushes to release channel - <font color="green">Build lead</font>
** QA verifies release channel - <font color="orange">QA Lead</font>
* QA verifies release channel - <font color="orange">QA Lead</font>


* Notify the world - <font color="blue">Project lead</font>
* Notify the world - <font color="blue">Project lead</font>
Line 82: Line 124:
** MDC Devnews  
** MDC Devnews  
** Post the [http://www.mozilla.org/news.html Press Release]
** Post the [http://www.mozilla.org/news.html Press Release]
When you have completed these steps, rinse, repeat. Every month...
canmove, Confirmed users
1,635

edits