Changes

Jump to: navigation, search

Releases/Checklist

1,349 bytes removed, 01:34, 29 January 2008
Checklist
* Development code freeze - <font color="red">Dev lead</font>
** Email release-drivers & build@ when all code is in with formal "Go" - <font color="redblue">Dev Project lead</font>
* Builds created (all locales) - <font color="green">Build lead</font>
** Email QA lead when finished - <font color="green">Build lead</font>
* Project lead creates 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
* 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 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)
* Draft release notes -------<font color="blue">Project lead</font>^ I'm to here ** Confirm release notes with updatingdev lead, QA lead, others as appropriate** Stage release notes, other website changes
* 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
** 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>
* L10n** Owner signoff as needed** Trademark review as needed** L10n Build - Build*** Capture the chosen nightly into the candidates directory*** Package up Notify the locales** Run Automated [[MozillaQualityAssurance:MetaDiff|MetaDiff]] test - Build** L10N locale spot checks - QA Lead** Testing by people with language skills** Update the shipped-locales file with the final locales and platforms - Project Lead** Update the [[L10n:Firefox_1.5_Releases|public wiki listing the shipped locales]] * Notify Affiliates** Mozilla Europe *** Tristan Nitot - nitot -at- mozilla-europe.org*** Peter Van der Beken - peterv -at- mozilla-europe.org*** Pascal Chevrel - pascal.chevrel -at- mozilla-europe.org** Mozilla Japan *** Gen Kanai - gen -at- mozilla-japan.org*** dynamis -at- mozilla-japan.org * Vulnerability Notice - dveditz** Draft to Security Group/Security-anncounce** Advisories posted on release** NEW: notify CERT (?) * Other PR as needed - Product** Web site updates * Release Notes ** Inputs to cbeard/basil - Dev/QA/Product** First Draft complete - ** Review - Dev/QA/Product** Final release notes -  * Final staging** Stage bits - Build*** Tue (UK time): cf to stage files in private area of ftp server, and transfer for signing*** Tue (MV time): preed/rhelmer to sign builds, juanb to email cf with go/no go on publishing builds*** Wed (UK time): cf to check signing log, gather installers, final check, push live by 0400 PDT (1200 BST), configure bouncer*** Wed (MV time): preed/rhelmer run releasetest verification (bouncer check), push updates when ready (~4pm)** '''Let IT know about release date 24-48 hrs ahead of time.''' world - <font color="blue">Project Lead*** Releases should NOT be scheduled in the morning.** Version IDlead</Update path test - QA Leadfont>** Make update paths/install bits live - Build*** Coordinate with IT to make sure current versions are pushed to the ''mozilla-current'' rsync module** Run automated [[MozillaQualityAssurance:Download_Checker|download checker]] - QA** Test live update/install bits - QA Lead** Dashboard stats tracking configuration/setup (oremj/webteam)** Post note to these places to annouce the release;*** all -at- mozilla.com (so all staff knows)*** drivers -at- mozilla.org (so drivers outside Mozilla Corp know)*** mozillam.dev.planning newsgroup*** mozillam.annouce announce newsgroup (all product release announcements are expected here)** MDC Devnews
** Post the [http://www.mozilla.org/news.html Press Release]
 
* Special CJK builds for Yahoo and Google
** These are builds with yahoo specific search codes
** The are due within 2 weeks of the main product release
** Generate builds - Build
** Test the builds - QA
** Release the builds to the respective venders - Build
1,457
edits

Navigation menu