Changes

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: </font>* <font color="red">Security/Dev lead: </font>* <font color="green">Build lead: </font>* <font color="orange">QA lead: </font>

== Checklist ==* Meet and schedule release - <font color="blue"strong>Project lead:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp;&nbsp; ALUMNO/AS DE PROGRAMA MODULAR DE LA UNEDEntire team</fontstrong>

*Decision on release date - <font color="red"strong>Security/Dev lead: &nbsp;&nbsp; PARA LA EDUCACION Y LA INFORMACIONEntire team</fontstrong> *<font color="red">* Update [[Http://labs.mozilla.com/ labs.mozilla.com/Releases]]</font> *page - <font color="greenblue">Build Project lead: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; trabajo de la alumna Gilma Gámez López</font> ** Update Releases/PRODUCT&VERSION with proposed schedule - <font color="greenblue">Project lead</font> ** Email dev-planning and release-drivers with proposed schedule - <font color="orangeblue">QA 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 blockers - <font color= Checklist ="blue">Project lead</font>** Alert developers of upcoming freeze - <font color="blue">Project lead</font>

*Meet and schedule release Development code freeze - '''Entire team'''<font color="red">Dev lead</font>** Hand off to QA for verifications - <font color="orange">QA Lead</font>

*Decision on release date - '''Entire team''' Ready for builds**Update [[Releases]] page Email release-drivers when all code is in with formal "Go" - <font color="blue">Project lead</font> **Update Releases/PRODUCT&amp;VERSION with proposed schedule File a bug to make sure there is no crash report throttling - <font color="blue">Project lead</font> **Email dev-planning * For 1.9.0, include timestamp and releasebonsai URI down to the last checkin. Specify timezone in email as well (PST vs PDT).*** For 1.9.1, include a changeset*** Specify l10n cut off (1.9.0-drivers with proposed schedule only) as well** File a bug to update versions in AMO - <font color="blue">Project lead</font>

*Triage of blocking/approval requests as needed - '''Entire team Builds created (minus buildall locales)''' **Schedule meetings - <font color="bluegreen">Project Build lead</font> **Alert developers of blockers Email release- <font color="blue">Project lead</font> **Alert developers of upcoming freeze drivers when builds are created - <font color="bluegreen">Project Build lead</font>

*Development code freeze QA tests builds - <font color="redorange">Dev leadQA Lead</font> **Hand 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>** When signed off to QA for verifications , email release-drivers with notification - <font color="orange">QA Lead</font>

*Ready for builds **Email release-drivers when all code is in with formal "Go" Build snippets on betatest channel - <font color="bluegreen">Project Build lead</font> **File a bug to make sure there is no crash report throttling - <font color="blue">Project Email QA 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 ***Specify l10n cut off (1.9.0-only) as well **File a bug to update versions in AMO when finished - <font color="bluegreen">Project Build lead</font>

*Builds created (all locales) - <font color="green">Build Project lead</font> **Email creates [[Webtools:Release_Notes|beta release-drivers when builds are created notes]]; staging and live - <font color="greenblue">Build leadProject Lead</font>

*QA tests builds - <font color="orange">QA Lead</font> **QA completes testing verifies snippets and website and maps it onto their test plan page (usually at Releases/PRODUCTNAME_VERSION/Test_Plan on the wiki) emails release- <font color="orange">QA Lead</font> **When drivers when signed off, email release-drivers with notification - <font color="orange">QA Lead</font>

*Build snippets on betatest channel If any of those fail, email release- <font color=drivers with a formal "stop" notification and a second "greengo">Build lead</font> **Email QA lead notification when finished the process is started again - <font color="greenblue">Build leadProject Lead</font>

*Project lead creates [[Webtools:Release Notes|"Go" to beta ** Formal "Go" email sent to release notes]]; staging and live -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>

*QA verifies snippets and website and emails Beta period** Announce to release-drivers when signed off , m.d.a.<application> (i.e. thunderbird or 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 infra** Notify PR (melissa) of "we're shipping in a week" estimate - <font color="blue">Project lead</font>** 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>** Make sure the release looks correct in the crash-stats admin - <font color="blue">Project lead</font>

*If any of those fail, email release-drivers with a formal "stop" notification and a second "go" notification when the process is started again Vulnerability notices - <font color="bluered">Project LeadSecurity lead</font>** Draft to Security Group/Security-anncounce** Notify CERT (as needed)

*"Go" to beta **Formal "Go" email sent to [[Webtools:Release_Notes|Draft release-drivers notes]] - <font color="blue">Project lead</font> **Build snippets pushed to beta channel Confirm release notes with dev lead, QA lead, others as appropriate** Stage release notes, other website changes** Vet past marketing (jslater@m.c)** Alert Mozilla Europe/Japan/China as soon as release notes (and product-details bug) are ready - <font color="greenblue">Build Project lead</font> **QA verifies snippets on beta channel * Be sure to give them the estimated release date and time.** Alert webdev (wenzel/clouserw/morgamic) of when release is planned for (for product-details pushing) - <font color="orangeblue">QA LeadProject lead</font>

*Beta period Decision to release - <strong>Entire team</strong>**Announce to release-driversIf yes, m.d.a.&lt;application&gt; let IT (i.e. thunderbird or firefoxinfra), m.announce.prerelease, m.d.planning know 24-48 hours ahead of time based on [[Build:ReleasePolicy|release policy]] - <font color="blue">Project lead</font> **Notify mirrors of beta release File a bug to make sure we throttle crash reports - <font color="blue">Project lead</font> emails infra **Notify PR (melissa@m.c) of "we're shipping in a week" estimate - <font color="blue">Project lead<x days/font> **Announce to [https:hours//intranet.mozilla.org/Firefox:SecurityVendors AV/Firewall vendors] - <font color=minutes"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> **Make sure the release looks correct in the crash-stats admin estimate - <font color="blue">Project lead</font>

*Vulnerability notices Final Release** 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>** 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> **Draft QA verifies website changes - <font color="orange">QA Lead</font>** Build pushes to Security Grouprelease channel - <font color="green">Build lead</Security-anncounce font>**Notify CERT (as needed)QA verifies release channel - <font color="orange">QA Lead</font>

*[[Webtools:Release Notes|Draft release notes]] - <font color="blue">Project lead</font> **Confirm release notes with dev lead, QA lead, others as appropriate **Stage release notes, other website changes **Vet past marketing (jslater@m.c) **Alert Mozilla Europe/Japan/China as soon as release notes (and product-details bug) are ready - <font color="blue">Project lead</font> ***Be sure to give them the estimated release date and time. **Alert webdev (wenzel/clouserw/morgamic) of when release is planned for (for product-details pushing) - <font color="blue">Project lead</font> *Decision to release - '''Entire team''' **If yes, let IT (infra) know 24-48 hours ahead of time based on [[Build:ReleasePolicy|release policy]] - <font color="blue">Project lead</font> **File a bug to make sure we throttle crash reports - <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 **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> **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> **QA verifies website changes - <font color="orange">QA Lead</font> **Build pushes to release channel - <font color="green">Build lead</font> **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) **m.dev.planning newsgroup **m.announce newsgroup (all product release announcements are expected here) **MDC Devnews **Post the [http://www.mozilla.org/news.html Press Release]