Firefox:1.5.0.4:Release Checklist: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 3: Line 3:
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.
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.
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


* Development code freeze - Project Lead
* Initial verification - QA Lead
* Initial verification - QA Lead
** Complete Bug Verification Target - QA Lead
** Complete Bug Verification Target - QA Lead
** BFT on one platform - QA Lead
** BFT on one platform - QA Lead
* Complete Regression Testing - QA Lead
* Complete Regression Testing - QA Lead
** Examples: All BFTs/FFTs, JS regression test, Security regressin test, top sites, top extensions, etc.  See Test Plan for details.
** Examples: All BFTs/FFTs, JS regression test, Security regression test, top sites, top extensions, etc.  See Test Plan for details.
 
* En-US Release Candidates
* En-US Release Candidates
** Release Prep - Build
** Release Prep - Build
** en-US Install/Startpage/Version ID/Udpate test - QA Lead
** en-US Install/start page/Version ID/Update test - QA Lead
* RC Release
* RC Release
** Annouce to community
** Announce to community
** Watch blogs and groups
** Watch blogs and news groups


* L10n
* L10n
Line 22: Line 25:
** Trademark review as needed
** Trademark review as needed
** L10n Build - Build
** L10n Build - Build
*** Capture the chosen nightly into the canidates directory
*** Capture the chosen nightly into the candidates directory
*** Package up the locales
*** Package up the locales
** L10N qualification testing - QA Lead
** Run Automated [[MozillaQualityAssurance:MetaDiff|MetaDiff]] test - QA Lead
** Testing by person with language skills
** 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]]
 
* Software Updates
** build software update mar files - Build
** setup Bouncer and AUS2 links - Build
** Run automated [[MozillaQualityAssurance:Update_Checker|Update Checker]] - QA
** Spot check combination of update paths, locales, and platforms - QA Lead


* Annouce to partners/distibuter - basil
* Announce to partners/distributer - basil
** Symantec
** Symantec
** McAfee
** McAfee
** Need at least a week notice
** Need at least a week notice
* 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
* Announce to security group - dveditz
* Announce to security group - dveditz
** security group
** to security and security-announce aliases
** Aecurity annouce
** 1-2 weeks out
** 1-2 weeks out
* Vulnerability Notice - dveditz
* Vulnerability Notice - dveditz
** Draft to Sec/Secannc
** Draft to Security Group/Security-anncounce
** Adviseries posted on release
** Advisories posted on release
 
* Other PR as needed - Product
* Other PR as needed - Product
** Web site updates
** Web site updates
* Release Notes  
* Release Notes  
** Inputs to rebron - Dev/QA/Product
** Inputs to cbeard/basil - Dev/QA/Product
** First Draft complete -  cbeard
** First Draft complete -  cbeard
** Review - Dev/QA/Product
** Review - Dev/QA/Product
** Final release notes - cbeard
** Final release notes - cbeard
* Final staging
* Final staging
** Stage bits - Build
** Stage bits - Build
** Run automated check - QA Lead
** Let IT know about release date 24-48 hrs ahead of time. - Project Lead
** Version ID/Update path test - QA Lead
** Version ID/Update path test - QA Lead
** Make updatepaths/install bits live - Build
** Make update paths/install bits live - Build
** Test live update/install bigs - QA Lead
** Run automated [[MozillaQualityAssurance:Download_Checker|download checker]] - QA Lead
** Test live update/install bits - QA Lead
 
* Special CJK builds for Yahoo and Google  
* Special CJK builds for Yahoo and Google  
** These are builds with yahoo specific search codes
** These are builds with yahoo specific search codes

Latest revision as of 20:21, 30 May 2006

Firefox/Thunderbird 1.5.0.4 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
  • Software Updates
    • build software update mar files - Build
    • setup Bouncer and AUS2 links - Build
    • Run automated Update Checker - QA
    • Spot check combination of update paths, locales, and platforms - QA Lead
  • Announce to partners/distributer - basil
    • Symantec
    • McAfee
    • Need at least a week notice
  • 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
  • Announce to security group - dveditz
    • to security and security-announce aliases
    • 1-2 weeks out
  • Vulnerability Notice - dveditz
    • Draft to Security Group/Security-anncounce
    • Advisories posted on release
  • Other PR as needed - Product
    • Web site updates
  • Release Notes
    • Inputs to cbeard/basil - Dev/QA/Product
    • First Draft complete - cbeard
    • Review - Dev/QA/Product
    • Final release notes - cbeard
  • 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
    • Make update paths/install bits live - Build
    • Run automated download checker - QA Lead
    • Test live update/install bits - QA Lead
  • 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 lead
    • Release the builds to the respective venders - Build
Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox:1.5.0.4:Release_Checklist&oldid=26935"