View source for Releases/Thunderbird 2.0.0.12/Checklist

This is the general release checklist we should use for maintenance releases.

It is organized by major functional activity in roughly chronological order. At the end of each bullet is the owner of the checklist item from within the Release Team.

== Team ==
* <font color="blue">Project lead: ss</font>
* <font color="red">Security/Dev lead: dveditz</font>
* <font color="green">Build lead: nthomas</font>
* <font color="orange">QA lead: abillings</font>

== Checklist ==
* <s>Meet and schedule release - <strong>Entire team</strong>
** Email dev-planning and release-drivers to announce meeting (2 days in advance) - <font color="blue">Project lead</font>
** Have meeting - <font color="blue">Led by Project lead</font>

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

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

* Development code freeze - <font color="red">Dev lead</font>
** Email release-drivers when all code is in with formal "Go" - <font color="blue">Project lead</font>
*** Include bonsai URI from last 24 hours. Specify timezone in email as well (PST vs PDT).

* Builds created (all locales) - <font color="green">Build lead</font>
** Email release-drivers when builds are created - <font color="green">Build lead</font>
** Email betatesters when builds are created - <font color="blue">Project lead</font>

* QA verification - <font color="orange">QA Lead</font>
** QA completes testing and maps it onto their test plan page (usually at PRODUCTNAME:VERSION:Test_Plan on the wiki) - <font color="orange">QA Lead</font>
** When signed off, email release-drivers with notification - <font color="orange">QA Lead</font>

* Build snippets on betatest channel - <font color="green">Build lead</font>
** Email QA lead when finished - <font color="green">Build lead</font>

* Project lead creates [[Webtools:Release_Notes|beta release notes]]; staging and live - <font color="blue">Project Lead</font>

* QA verifies snippets and website and emails release-drivers when signed off - <font color="orange">QA Lead</font>

* "Go" to beta
** Formal "Go" email sent to release-drivers - <font color="blue">Project lead</font>
** Build snippets pushed to beta channel - <font color="green">Build lead</font>
** QA verifies snippets on beta channel - <font color="orange">QA Lead</font>

* Beta period
** Announce to release-drivers, m.d.a.firefox, m.announce.prerelease, m.d.planning - <font color="blue">Project lead</font>
** Notify mirrors of beta release - <font color="blue">Project lead</font> emails Justin
** Announce to [https://intranet.mozilla.org/Firefox:SecurityVendors AV/Firewall venders] - <font color="blue">Project lead</font>
** Announce to security group - <font color="red">Security lead</font>
*** to security and security-announce aliases
** Monitor feedback - <font color="orange">QA Lead</font>, <font color="blue">Project lead</font>

* Vulnerability notices - <font color="red">Security lead</font>
** Draft to Security Group/Security-anncounce
** Notify CERT (as needed)</s>

* <s>[[Webtools:Release_Notes|Draft release notes]] - <font color="blue">Project lead</font>
** Confirm release notes with dev lead, QA lead, others as appropriate</s>
** <s>Stage release notes, other website changes
** Alert Mozilla Europe/Japan/China as soon as release notes are ready - <font color="blue">Project lead</font>
*** Be sure to give them the estimated release date and time.</s>

* <s>Decision to release - <strong>Entire team</strong>
** If yes, let IT know 24-48 hours ahead of time - <font color="blue">Project lead</font>

* Final Release
** Bits to mirrors - <font color="blue">Project lead</font> sends "go email"
*** Push actual bits - <font color="green">Build lead</font>
** Verify bits on releasetest channel - <font color="orange">QA Lead</font>
** Push website changes - <font color="blue">Project lead</font>
** Push security advisories - <font color="red">Security lead</font>
*** Don't forget the security center changes [http://www.mozilla.org/security/#Security_Alerts]
** QA verifies website changes - <font color="orange">QA Lead</font>
** Build pushes updates to release channel - <font color="green">Build lead</font></s>
** QA verifies release channel - <font color="orange">QA Lead</font>

* Notify the world - <font color="blue">Project lead</font>
** all -at- mozilla.com (so all staff knows)
** drivers -at- mozilla.org (so drivers outside Mozilla Corp know)
** m.dev.planning newsgroup
** m.announce newsgroup (all product release announcements are expected here)
** MDC Devnews 
*** Include note that Thunderbird 1.5 is unsupported.
** Post the [http://www.mozilla.org/news.html Press Release]