Firefox:Release:2.x:Release Checklist

From MozillaWiki
Jump to: navigation, search

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.
  • 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 - 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 public wiki listing the shipped locales
  • Announce to partners/distributer - basil
    • Symantec
    • McAfee
    • Need at least a week notice
  • Announce to security group - dveditz
    • to security and security-announce aliases
    • 1-2 weeks out
  • Software Updates
    • build software update mar files - Build
    • setup Bouncer and AUS2 links - Build
    • Run automated Update Checker - Build
    • Spot check combination of update paths, locales, and platforms - QA Lead
  • 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. - Project Lead
      • Releases should NOT be scheduled in the morning.
    • Version ID/Update path test - QA Lead
    • 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 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)
      • mozilla.dev.planning newsgroup
      • mozilla.annouce newsgroup (all product release announcements are expected here)
    • Post the 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
Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox:Release:2.x:Release_Checklist&oldid=72558"