Thunderbird/Release Driving/Beta Release Checklist: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 33: | Line 33: | ||
* Development code freeze - <font color="red">Dev lead</font> | * Development code freeze - <font color="red">Dev lead</font> | ||
* Co-ordinate with l10n <font color="blue">Project lead</font> | * Co-ordinate with l10n - <font color="blue">Project lead</font> | ||
* File bugs relating to the [file:///Users/moztest/comm/drivertools/bugfiling/new-beta-release.html beta release] - <font color="blue">Project lead</font> | |||
* Ready for builds | * Ready for builds | ||
| Line 63: | Line 65: | ||
** Email QA lead (via thunderbird-drivers) when finished - <font color="green">Build lead</font> | ** Email QA lead (via thunderbird-drivers) when finished - <font color="green">Build lead</font> | ||
* QA verifies snippets and website | * QA [[Thunderbird:Testing/Automated_Update_Testing|verifies snippets on betatest channel]] and checks website. Then emails thunderbird-drivers when signed off - <font color="orange">QA Lead</font> | ||
* 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> | * 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> | ||
| Line 69: | Line 71: | ||
=== Release Notes & Release === | === Release Notes & Release === | ||
* [http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugfiling/new- | * [http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugfiling/new-beta-release.html File bug] for bouncer entries (if not already) - <font color="blue">Project lead</font> | ||
** Note: Bouncer entries are required for Release Candidates as well as alphas & betas. | ** Note: Bouncer entries are required for Release Candidates as well as alphas & betas. | ||
* | * [[Webtools:Thunderbird_Release_Notes|Draft release notes]] - <font color="purple">Website lead</font> or <font color="blue">Project lead</font> | ||
** Stage release notes, other website changes | ** Stage release notes, other website changes | ||
** Confirm release notes with PR (rebron), QA lead, others as appropriate | |||
* Decision to release - <strong>Entire team</strong> | * Decision to release - <strong>Entire team</strong> | ||
** | ** If yes, notify mirrors of beta release about 24-48 hours ahead of time. Email justdave or infra - at - mozilla.com - <font color="blue">Project lead</font> | ||
** Notify PR | ** Notify PR of "we're shipping in x days/hours/minutes" estimate - <font color="blue">Project lead</font> | ||
*** This is normally done via rebron on tb-drivers with no special messages. | |||
* Final Release, in order: | * Final Release, in order: | ||
| Line 87: | Line 88: | ||
*#* Push actual bits to ftp / releases - <font color="green">Build lead</font> | *#* Push actual bits to ftp / releases - <font color="green">Build lead</font> | ||
*# Push website changes - <font color="blue">Project lead</font> | *# Push website changes - <font color="blue">Project lead</font> | ||
*# | *# Verify website changes - <font color="orange">QA Lead</font> | ||
*# Build pushes to beta channel - <font color="green">Build lead</font> | *# Build pushes to beta channel - <font color="green">Build lead</font> | ||
*# Verify bits on beta channel - <font color="orange">QA Lead</font> | *# [[Thunderbird:Testing/Automated_Update_Testing|Verify bits on beta 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> | ||
Revision as of 10:55, 29 July 2010
This is the general release checklist we should use for Thunderbird Alpha and Beta releases, and also Release Candidates.
It is based largely on Releases/Checklist but adapted specifically for Thunderbird.
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
- Project/Dev lead: Standard8
- Build lead: gozer
- QA lead: _Tsk_
- Website lead: rebron
- Support Lead: Roland
Checklist
Improve our processes! File bugs for improvements against bug 540394
Initial Stages
- Meet and schedule release - Entire team
- Project lead organises meeting/discussing. May typically be at driver meetings, but other mediums can be used if felt necessary - Project lead
- Decision on release date - Entire team
- Update Releases page - Project lead
- Update Releases/PRODUCT&VERSION with proposed schedule - Project lead
- Email thunderbird-drivers and post on Status Meeting (including weekly) with proposed schedule - Project lead
- Triage of blocking/approval requests as needed - Entire team (minus build)
- Schedule meetings - Project lead
- Alert developers of blockers - Project lead
- Alert developers of upcoming freeze - Project lead
- Development code freeze - Dev lead
- Co-ordinate with l10n - Project lead
- File bugs relating to the [file:///Users/moztest/comm/drivertools/bugfiling/new-beta-release.html beta release] - Project lead
- Ready for builds
- Email thunderbird-drivers when all code is in with formal "Go" - Project lead
- In Email include:
- comm-* revision
- mozilla-* revision
- dom-inspector revision
- LDAP CVS tag
- L10n revisions
- New Locales (also specify beta/release)
- In Email include:
- Email thunderbird-drivers when all code is in with formal "Go" - Project lead
- Email contacts with release schedules & build details - Project lead
- Crash-stats updated with new version details - Project lead
Build & QA
- Builds created (all locales) - Build lead
- Email thunderbird-drivers when builds are created - Build lead
- QA tests builds - QA Lead
- QA completes testing and maps it onto their test plan page (usually at Releases/PRODUCTNAME_VERSION/Test_Plan on the wiki) - QA Lead
- When signed off, email thunderbird-drivers with notification - QA Lead
- Verify against Virus vendors and announce to AV/Firewall vendors - _Tsk_
- Build snippets on betatest channel - Build lead
- Email QA lead (via thunderbird-drivers) when finished - Build lead
- QA verifies snippets on betatest channel and checks website. Then emails thunderbird-drivers when signed off - QA Lead
- If any of those fail, email thunderbird-drivers with a formal "stop" notification and a second "go" notification when the process is started again - Project Lead
Release Notes & Release
- File bug for bouncer entries (if not already) - Project lead
- Note: Bouncer entries are required for Release Candidates as well as alphas & betas.
- Draft release notes - Website lead or Project lead
- Stage release notes, other website changes
- Confirm release notes with PR (rebron), QA lead, others as appropriate
- Decision to release - Entire team
- If yes, notify mirrors of beta release about 24-48 hours ahead of time. Email justdave or infra - at - mozilla.com - Project lead
- Notify PR of "we're shipping in x days/hours/minutes" estimate - Project lead
- This is normally done via rebron on tb-drivers with no special messages.
- Final Release, in order:
- Bits to mirrors - Project lead sends "go email".
- Typical mirror saturation is 1 to 2 hours, the email should take account of this.
- Push actual bits to ftp / releases - Build lead
- Push website changes - Project lead
- Verify website changes - QA Lead
- Build pushes to beta channel - Build lead
- Verify bits on beta channel - QA Lead
- Bits to mirrors - Project lead sends "go email".
- Notify the world - Project lead
all -at- mozilla.com (so all MoCo staff knows)(apparently this doesn't currently happen)- staff -at- mozillamessaging.com (so all MoMo staff knows)
- tb-planning
- tb-enterprise (maybe, depends on release & feedback wanted).
- m.dev.apps.thunderbird, m.dev.apps.calendar, m.dev.l10n, m.dev.planning newsgroups
- MDC Devnews
- Email metrics mozilla.com with the new version details.