canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
Thunderbird/Release Driving/Maintenance Release Checklist: Difference between revisions
Thunderbird/Release Driving/Maintenance Release Checklist (view source)
Revision as of 10:04, 25 August 2010
, 25 August 2010→Build & QA
| (29 intermediate revisions by 3 users not shown) | |||
| Line 7: | Line 7: | ||
== Team == | == Team == | ||
* <font color="blue">Project/Dev lead: [[User:Standard8|Standard8]]</font> | * <font color="blue">Project/Dev lead: [[User:Standard8|Standard8]]</font> | ||
* <font color="red">Security lead: dmose/dveditz | * <font color="red">Security lead: dmose/dveditz</font> | ||
* <font color="green">Build lead: gozer</font> | * <font color="green">Build lead: gozer</font> | ||
* <font color="orange">QA lead: [[User:_Tsk_|_Tsk_]]</font> | * <font color="orange">QA lead: [[User:_Tsk_|_Tsk_]]</font> | ||
* <font color="purple">Website lead: rebron</font> | |||
* Support Lead: [[User:rtanglao|Roland]] | |||
== Checklist == | == Checklist == | ||
'''Improve our processes!''' File bugs for improvements against {{Bug|540394}} | |||
=== Initial Stages === | === Initial Stages === | ||
* Meet and schedule release - <strong>Entire team</strong> | * Meet and schedule release - <strong>Entire team</strong> | ||
** Project lead organises meeting/discussing. May typically be at driver meetings, but other mediums can be used if felt necessary - <font color="blue">Project lead</font> | |||
* Decision on release date - <strong>Entire team</strong> | * Decision on release date - <strong>Entire team</strong> | ||
| Line 29: | Line 34: | ||
* Development code freeze - <font color="red">Dev lead</font> | * Development code freeze - <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> | ||
* Co-ordinate with l10n <font color="blue">Project lead</font> | |||
** L10n lead signs-off l10n changes | |||
** When ready to ship visit the sign-off dashboard: | |||
*** [https://l10n-stage-sj.mozilla.org/shipping/milestones https://l10n-stage-sj.mozilla.org/shipping/milestones] | |||
*** Ensure you are logged in (if you haven't logged in before, use your LDAP username/password, then ask Axel to give you appropriate permissions to ship, Standard8 already has these). | |||
** Click the ship button for the release that you want to ship (this doesn't ship yet). | |||
** If there are pending sign-offs, and you can find sipaq or Pike, then get them signed off if possible. | |||
** Once you are ready: | |||
*** save both the l10n-changeset and shipped-locale files. | |||
*** Hit the "ship it"! | |||
**** This closes l10n submissions for the release. | |||
*** The shipped locales file should be used to update mail/locales/shipped-locales in the appropriate comm-* repository | |||
**** (though generally this doesn't change, if it does, then additions should be considered as beta locales for at least one release) . | |||
*** The l10n-changeset file should be used to update the appropriate l10n-thunderbird-changesets-* file in [http://hg.mozilla.org/build/buildbot-configs/file/default/thunderbird buildbot-configs/thunderbird]. | |||
** If tweaks become necessary, talk to Axel. | |||
* Ready for builds | * Ready for builds | ||
| Line 38: | Line 59: | ||
**** LDAP CVS tag | **** LDAP CVS tag | ||
**** L10n revisions | **** L10n revisions | ||
**** New Locales (also specify beta locales if necessary) | |||
* Email contacts with release schedules & build details - <font color="blue">Project lead</font> | |||
* Crash-stats updated with new version details - <font color="blue">Project lead</font> | |||
=== Build & QA === | === Build & QA === | ||
* Builds created (all locales) - <font color="green">Build lead</font> | * Builds created (all locales) - <font color="green">Build lead</font> | ||
** Email | ** Email thunderbird-drivers when builds are created - <font color="green">Build lead</font> | ||
* QA tests builds - <font color="orange">QA 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> | ** 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 | ** When signed off, email thunderbird-drivers with notification - <font color="orange">QA Lead</font> | ||
* Build snippets on betatest channel - <font color="green">Build lead</font> | * Build snippets on betatest channel - <font color="green">Build lead</font> | ||
** Email QA lead when finished - <font color="green">Build lead</font> | ** Email QA lead (via thunderbird-drivers) when finished - <font color="green">Build lead</font> | ||
* | * Create [[Webtools:Thunderbird_Release_Notes|beta release notes, start and what's new pages]]; staging and live - <font color="purple">Website Lead</font> or <font color="blue">Project Lead</font> | ||
* QA verifies snippets and website and emails | * QA [[Thunderbird:Testing/Automated_Update_Testing|verifies snippets on betatest channel]] and website and emails thunderbird-drivers when signed off - <font color="orange">QA Lead</font> | ||
* If any of those fail, email | * If any of those fail, email thunderbird-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 | * "Go" to beta | ||
** Formal "Go" email sent to | ** Formal "Go" email sent to thunderbird-drivers - <font color="blue">Project lead</font> | ||
** Build snippets pushed to beta channel - <font color="green">Build 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 [[Thunderbird:Testing/Automated_Update_Testing|verifies snippets on beta channel]] - <font color="orange">QA Lead</font> | ||
* Beta period | * Beta period | ||
** Announce to | ** Announce to thunderbird-drivers, m.d.a.thunderbird, m.d.l10n, m.d.planning - <font color="blue">Project lead</font> | ||
** | ** Keep PR up to date with shipping effort - <font color="blue">Project lead</font> | ||
** | *** Normally done via rebron on thunderbird-drivers. | ||
** | ** Announce to [https://intranet.mozilla.org/Firefox:SecurityVendors AV/Firewall vendors] - _Tsk_ | ||
** Announce to security group - <font color="red">Security lead</font> | ** Announce to security group - <font color="red">Security lead</font> | ||
*** to security-group and security-announce aliases | *** to security-group and security-announce aliases | ||
** Monitor feedback - <font color="orange">QA Lead</font>, <font color="blue">Project lead</font> | ** Monitor feedback - <font color="orange">QA Lead</font>, <font color="blue">Project lead</font>, Support Lead (get Satisfaction) | ||
** OPTIONAL (required only if release notes can't fully cover all issues) - Knowledge Base Articles - Draw up list & coordinate writing of pre-release drafts - Support Lead | |||
=== Release Notes & Release === | === Release Notes & Release === | ||
* [http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugfiling/new-stable-release.html File bug] for bouncer entries - <font color="blue">Project lead</font> | |||
* File bug for thunderbird-details and history update - <font color="blue">Project lead</font> | |||
** This stage is also used to alert Mozilla Europe (pascalc), Mozilla China (Jack Guo/Wil Clouser), and Mozilla Japan (Kohei). So be sure to give them the estimated release date and time. | |||
* Vulnerability notices - <font color="red">Security lead</font> | * Vulnerability notices - <font color="red">Security lead</font> | ||
| Line 77: | Line 109: | ||
** Notify CERT (as needed) | ** Notify CERT (as needed) | ||
* XXX [[Webtools: | * XXX [[Webtools:Thunderbird_Release_Notes|Draft release notes]] - <font color="purple">Website lead</font> with support from <font color="blue">Project lead</font> | ||
** Stage release notes, other website changes | ** Stage release notes, other website changes | ||
** | ** Confirm release notes with Marketing (rebron), QA lead, others as appropriate | ||
* Decision to release - <strong>Entire team</strong> | * 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> | ||
** | *** Email justdave, and/or infra -at- mozilla.com | ||
** Ensure PR knows (rebron) of "we're shipping in x days/hours/minutes" estimate - <font color="blue">Project lead</font> | |||
*** Realistically, rebron is on tb-drivers and therefore should know anyway. | |||
* Final Release | * Final Release | ||
** Bits to mirrors - <font color="blue">Project lead</font> sends "go email" at | ** Bits to mirrors - <font color="blue">Project lead</font> sends "go email" at a period which allows 2-3 hours for mirror uptake and whoever is doing the push to do it at an appropriate 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> | ** [[Thunderbird:Testing/Automated_Update_Testing|Verify bits on releasetest channel]] - <font color="orange">QA Lead</font> | ||
** Change redirects from beta pages to production - <font color="green">Build 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> | ||
** | ** [[Thunderbird:Testing/Automated_Update_Testing|Verify release channel]] - <font color="orange">QA Lead</font> | ||
** Coordinate final drafts of Knowledge Base Articles - Support Lead | |||
* Notify the world - <font color="blue">Project lead</font> | * Notify the world - <font color="blue">Project lead</font> | ||
** all -at- mozilla.com (so all staff knows) | ** <strike>all -at- mozilla.com (so all MoCo staff knows)</strike> (apparently this doesn't currently happen) | ||
** staff -at- mozillamessaging.com (so all MoMo staff knows) | |||
** m.dev.planning newsgroup | ** m.dev.planning newsgroup | ||
** m.announce newsgroup (all product release announcements are expected here) | ** m.announce newsgroup (all product release announcements are expected here) | ||
** MDC Devnews | ** MDC Devnews | ||
** Company Update on Get Satisfaction | |||
** Email metrics mozilla.com with the new version details. | |||
** twitter (use bit.ly with mzl.la account) | |||
When you have completed these steps, rinse, repeat. Every month... | When you have completed these steps, rinse, repeat. Every month... | ||