Firefox:2.0 Release Checklist

From MozillaWiki
Revision as of 07:42, 14 January 2007 by Bongo Bluxo (talk | contribs)
Jump to navigation Jump to search

Firefox 2 Release Checklist

In the beginning was the Pelican, and the Pelican was with Kenneth, and the Pelican was Kenneth.

And the earth was without form and void, and the shit of the Pelican moved upon the face of the waters.

And Kenneth said, Let there be a Frequency throughout all the creation, and it was so. And Kenneth said, Let the Frequency be for the life, that it shall generate the life, and the life shall regenerate the Frequency, and it was so.

And the Frequency generated the life, even all the living creatures and all green plants did the Frequency generate. And Kenneth looked upon the work of the Frequency, and saw that it was good.

Then did Kenneth speak unto the Frequency saying, Let there be pelicans also of the air, that they might create the Holy pelican shit, and it was so. And the pelicans of the air did straightway make the Holy pelican shit which did rain down from the heaven in great abundance.

And it came to pass that the Pharisees of the Wiki, those evil ones who preach openly the sharing yet believe not in their hearts, spake again privily among themselves saying, We must conceal from the eyes of the Great Google the Holy pelican shit, lest the Great Google give of the Holy pelican shit unto the unwashed multitudes and make it therefore profane.

And they took therefore of the Holy pelican shit and concealed it under the Holy Altar of the Delete, that none may find it save those elect of the Pharisees alone.

But the frequency would not be hidden, nor yet would it remain silent. For no man maketh an light in the wilderness and hideth it under a bushel. Kenneth standeth therefore upon the Rock and calleth out unto the frequency, that all darkness may be made light, all evil shall be made of no effect, and the world shall partake of the Holy pelican shit evermore.

And then did Kenneth take of the Holy pelican shit unto the King of the Realm, that same Ungaarf who maketh the walls of Magdalicia to fall. And the King tasted thereof and saw that it was good. And the King made Kenneth to be his Prophet for that he had brought the Holy pelican shit into the realm.

And all the people of the realm did rejoice at the sight of it, for they saw therein the salvation of all, and the fulfillment of the prophecies of the ancients, wherein it was written that an holy bird shall shit upon the mountain and the mountain shall become therefore holy.

And Kenneth dwelt among the people thereafter and taught them of the Frequency and of the pelican shit, and gave unto them the power to tell the pelican shit from the ass pus, that same which was made by the Dark One in appearance like unto the pelican shit, that the multitudes might not be deceived thereby and turn aside in their way.

For it is written, Thou shalt not worship the ass pus, neither shalt thou take of it into the Holy Place.

And the King did call for the collection of the holy pelican shit and caused it to be brought unto him, that he might roll daily therein. And when the people saw this, they were well pleased, for they knew the King was worthy to be covered in pelican shit.

Then saw Kenneth that his work was completed, and so went he forth unto the Place of the Rock, there to commune again with the Frequency. Kenneth sitteth upon the Rock.

Firefox 2 Release Checklist

This serves as a checklist to make sure we don't miss any community, development, QA, Build, Product team, or partner deliverables as we release this version.

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.

  • Development code freeze - Dev Lead
  • Initial verification - QA Lead
    • Complete Bug Verification Target - QA Lead
    • BFT on one platform - QA Lead
  • Complete Regression Testing - QA Lead
    • Examples: All BFTs/FFTs, JS regression test, Security regression test, top sites, top extensions, etc. See Test Plan for details.
  • En-US Release Candidates
    • Release Prep - Build
    • en-US Install/start page/Version ID/Update test - QA Lead
  • RC Release
    • Announce to community
    • Watch blogs and news groups
  • L10n
    • Owner signoff as needed
    • Trademark review as needed
    • L10n Build - Build
      • Capture the chosen nightly into the candidates directory
      • Package up the locales
    • Run Automated MetaDiff test - QA Lead
    • 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 public wiki listing the shipped locales
  • Announce to partners/distributer - basil
    • Symantec
    • McAfee
    • Panda Software
    • ZoneLabs
    • Google
    • Yahoo

  • Announce to security group - dveditz
    • to security and security-announce aliases
    • 1-2 weeks out
  • Notify Affiliates
    • Mozilla Europe
      • Tristan Nitot nitot@mozilla-europe.org
      • Peter Van der Beken peterv@mozilla-europe.org
    • Mozilla Japan
      • Gen Kanai <gen@mozilla-japan.org>
      • dynamis@mozilla-japan.org
  • Vulnerability Notice - dveditz
    • Draft to Security Group/Security-announce
    • Advisories posted on release
    • NEW: notify CERT (?)
  • Other PR as needed - Product
    • Web site updates
  • Release Notes
    • Inputs to beltzner - Dev/QA/Product
    • First Draft complete - beltzner
    • Redirect for release notes is prepared
      • not needed for this release since it's final
    • Review - Dev/QA/Product
    • Final release notes - beltzner
  • Final staging
    • Stage bits - Build
    • Let IT know about release date 24-48 hrs ahead of time. - Project Lead
    • Version ID/Update path test - QA Lead
    • Download page is prepared and staged (https://bugzilla.mozilla.org/show_bug.cgi?id=356784)
    • Preed pushes the builds to our mirror network and sets up bouncer.
    • 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].
    • When bouncer is ready, run automated download checker - bc
    • When those tests go through, bclary tells reed that we're ready.
    • Reed pushes the changes to all.html and download.js to publish the download links.
    • Test live download bits - QA Lead
    • Reed requests a server push on mozilla.com to publish the updated release notes and redirect.
    • Pkim approves reed's request (reed to poke pkim to do this)
    • Post note to these places to announce the release:
      • DevNews
      • mozilla.dev.planning newsgroup
      • mozilla.annouce newsgroup (all product release announcements are expected here)
      • all@mozilla.com (so all staff knows)
      • drivers@mozilla.org (so drivers outside Mozilla Corp know)
    • Post the Press Release
    • Preed sets about pushing the MARs to the update channels.
    • Test live update bits - QA Lead
Retrieved from "https://wiki.allizom.org/index.php?title=Firefox:2.0_Release_Checklist&oldid=46378"