Firefox:2.0 Release Checklist: Difference between revisions

Jump to navigation Jump to search
Line 45: Line 45:


* Announce to security group - dveditz
* Announce to security group - dveditz
** to security and security-announce aliases
** <strike>to security and security-announce aliases</strike>
** 1-2 weeks out
** 1-2 weeks out


Line 62: Line 62:


* Other PR as needed - Product
* Other PR as needed - Product
** Web site updates
** <strike> Web site updates</strike>


* Release Notes  
* Release Notes  
** Inputs to beltzner - Dev/QA/Product
** <strike>Inputs to beltzner - Dev/QA/Product</strike>
** <strike>First Draft complete -  beltzner</strike>
** <strike>First Draft complete -  beltzner</strike>
*** (https://bugzilla.mozilla.org/show_bug.cgi?id=356782)
*** (https://bugzilla.mozilla.org/show_bug.cgi?id=356782)
Line 77: Line 77:
** <strike>Let IT know about release date 24-48 hrs ahead of time. - Project Lead</strike>
** <strike>Let IT know about release date 24-48 hrs ahead of time. - Project Lead</strike>
** Version ID/Update path test - QA Lead
** Version ID/Update path test - QA Lead
** Download page is prepared and staged (https://bugzilla.mozilla.org/show_bug.cgi?id=356784)
** <strike>Download page is prepared and staged</strike> (https://bugzilla.mozilla.org/show_bug.cgi?id=356784)
** Preed pushes the builds to our mirror network and sets up bouncer.
** <strike>Preed pushes the builds to our mirror network and sets up bouncer.</strike>
** Download page is replaced with "We're releasing today, not ready yet, expect it at [ETA] message". I suggest somewhere in the 3-5pm PDT range, myself [beltzner].
** <strike>Download page is replaced with "We're releasing today, not ready yet, expect it at [ETA] message". I suggest somewhere in the 3-5pm PDT range, myself [beltzner].</strike>
** When bouncer is ready, run automated [[MozillaQualityAssurance:Download_Checker|download checker]] - bc
** <strike>When bouncer is ready, run automated [[MozillaQualityAssurance:Download_Checker|download checker]] - bc</strike>
** When those tests go through, bclary tells reed that we're ready.
** <strike>When those tests go through, bclary tells reed that we're ready.</strike>
** Reed pushes the changes to all.html and download.js to publish the download links.
** <strike>Reed pushes the changes to all.html and download.js to publish the download links.</strike>
** Test live download bits - QA Lead
** <strike>Test live download bits - QA Lead</strike>
** Reed requests a server push on mozilla.com to publish the updated release notes and redirect.
** <strike>Reed requests a server push on mozilla.com to publish the updated release notes and redirect.</strike>
** Pkim approves reed's request (reed to poke pkim to do this)
** <strike>Pkim approves reed's request (reed to poke pkim to do this)</strike>
** Schrep/mconnor - Post note to these places to announce the release:
** Post note to these places to announce the release:
*** DevNews
*** <strike>DevNews</strike>
*** mozilla.dev.planning newsgroup (it's waiting as a draft on DevNews)
*** <strike>mozilla.dev.planning newsgroup</strike>
*** mozilla.annouce newsgroup (all product release announcements are expected here)
*** mozilla.annouce newsgroup (all product release announcements are expected here)
*** all@mozilla.com (so all staff knows)
*** all@mozilla.com (so all staff knows)
*** drivers@mozilla.org (so drivers outside Mozilla Corp know)
*** drivers@mozilla.org (so drivers outside Mozilla Corp know)
*** DevNews
** <strike>Post the [http://www.mozilla.org/news.html Press Release]</strike>
** Post the [http://www.mozilla.org/news.html Press Release]
** Preed sets about pushing the MARs to the update channels.  
** Preed sets about pushing the MARs to the update channels.  
** Test live update bits - QA Lead
** Test live update bits - QA Lead
Confirmed users, Bureaucrats and Sysops emeriti
3,599

edits

Navigation menu