canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
Releases/Checklist: Difference between revisions
Jump to navigation
Jump to search
m
Reverted edits by Gilma.gamez (talk) to last revision by Clegnitto
Gilma.gamez (talk | contribs) (gilma gamez uned alumna) |
m (Reverted edits by Gilma.gamez (talk) to last revision by Clegnitto) |
||
| Line 1: | Line 1: | ||
This is the general release checklist we should use for maintenance releases. | 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. | 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 | == 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 - <strong>Entire team</strong> | |||
*< | * 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> | |||
*<font color=" | ** Email dev-planning and release-drivers with proposed schedule - <font color="blue">Project lead</font> | ||
*<font color=" | |||
== | * 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="blue">Project lead</font> | |||
** Alert developers of upcoming freeze - <font color="blue">Project lead</font> | |||
* | * Development code freeze - <font color="red">Dev lead</font> | ||
** Hand off to QA for verifications - <font color="orange">QA Lead</font> | |||
* | * Ready for builds | ||
** | ** Email release-drivers when all code is in with formal "Go" - <font color="blue">Project lead</font> | ||
** | ** File a bug to make sure there is no crash report throttling - <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 | |||
*** Specify l10n cut off (1.9.0-only) as well | |||
** File a bug to update versions in AMO - <font color="blue">Project lead</font> | |||
* | * Builds created (all locales) - <font color="green">Build lead</font> | ||
** Email release-drivers when builds are created - <font color="green">Build lead</font> | |||
** | |||
* | * QA tests builds - <font color="orange">QA Lead</font> | ||
** | ** 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, 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 | * QA verifies snippets and website and emails release-drivers when signed off - <font color="orange">QA 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 - <font color="blue">Project 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.<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> | |||
* | * Vulnerability notices - <font color="red">Security lead</font> | ||
** Draft to Security Group/Security-anncounce | |||
** Notify CERT (as needed) | |||
* | * [[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 - <strong>Entire team</strong> | ||
** | ** 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) of "we're shipping in | ** 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] | |||
*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] | |||
When you have completed these steps, rinse, repeat. Every month... | When you have completed these steps, rinse, repeat. Every month... | ||