Firefox:2.0 Release Checklist

Firefox 2 Release Checklist

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
    • (https://bugzilla.mozilla.org/show_bug.cgi?id=356782)
  • 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 -a-t- mozilla -d-o-t- 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