QA/Execution/Web Testing/MDN/ReleaseChecklist: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "== Team == * <font color="blue">Product lead: Jay Patel</font> * <font color="brown">Dev lead: Ozten King/Craig Cook</font> * <font color="orange">QA lead: Raymond</font> * <font...")
 
m (→‎Get Set: Moved prod tag up earlier)
 
(4 intermediate revisions by 2 users not shown)
Line 7: Line 7:
== Get Ready ==
== Get Ready ==
# Decision on release date and features - <Font color="blue">Product</font>/<Font color="brown">Dev Lead</font>
# Decision on release date and features - <Font color="blue">Product</font>/<Font color="brown">Dev Lead</font>
# Triage of blocking/approval requests as needed - <Font color="blue">Product</font>/<Font color="brown">Dev Lead</font>
# Triage of blocking/approval requests as needed - <Font color="blue">Product</font>/<Font color="brown">Dev Lead</font>/<font color="orange">QA lead</font>
# Update staging data from prod if necessary.
# Update staging data from prod if necessary.


Line 14: Line 14:
# File push bug in mozilla.org/Server Operations - Web Content Push - <font color="blue">Dev lead</font>
# File push bug in mozilla.org/Server Operations - Web Content Push - <font color="blue">Dev lead</font>
#* Offer a date and time to IT - <font color="blue">Dev lead</font>
#* Offer a date and time to IT - <font color="blue">Dev lead</font>
#* Add deployment time to [[Webdev:Releases]] calendar
# Extract strings
# Enact a code freeze - <font color="brown">Dev lead</font>
# Enact a code freeze - <font color="brown">Dev lead</font>
#* Email team with notification
#* Email team with notification
#* Email l10n <font color="blue">Product lead</font>
# Staging verification - <font color="orange">QA Lead</font>
# Staging verification - <font color="orange">QA Lead</font>
#* QA performs release testing
#* QA performs release testing
#* When signed off, email team with notification
#* When signed off, email team with notification
#* Update push bug with QA sign off
#* Update push bug with QA sign off
#* Confirm release notes with Dev lead, QA lead, others as appropriate
#* Create Production Branch <font color="brown">Dev lead</font>
# Determine a Go or no Go - <font color="blue">Product lead</font>
# Determine a Go or no Go - <font color="blue">Product lead</font>
#* If '''No Go''', email team with a formal "stop" notification and a second "go" notification when the process is started again
#* If '''No Go''', email team with a formal "stop" notification and a second "go" notification when the process is started again
#* If '''Go''', mention on push bug and email team ahead of time.  
#* If '''Go''', mention on push bug and email team ahead of time.  
#**Make sure an IT lead is assigned to the bug and there is a push time.
#**Make sure an IT lead is assigned to the bug and there is a push time.
#** Tag the branch for release with the appropriate version - <font color="brown">Dev lead</font>


== Go! ==
== Go! ==
# Push to production at assigned time - <font color="green">IT lead</font>
# Push to production at assigned time - <font color="green">IT lead</font>
# QA verifies production changes - <font color="orange">QA Lead</font>
# QA verifies production changes - <font color="orange">QA Lead</font>
# Send out the blogpost - <font color="blue">Product lead</font>

Latest revision as of 18:04, 3 December 2010

Team

  • Product lead: Jay Patel
  • Dev lead: Ozten King/Craig Cook
  • QA lead: Raymond
  • IT lead: push bug assignee

Get Ready

  1. Decision on release date and features - Product/Dev Lead
  2. Triage of blocking/approval requests as needed - Product/Dev Lead/QA lead
  3. Update staging data from prod if necessary.


Get Set

  1. File push bug in mozilla.org/Server Operations - Web Content Push - Dev lead
    • Offer a date and time to IT - Dev lead
    • Add deployment time to Webdev:Releases calendar
  2. Extract strings
  3. Enact a code freeze - Dev lead
    • Email team with notification
    • Email l10n Product lead
  4. Staging verification - QA Lead
    • QA performs release testing
    • When signed off, email team with notification
    • Update push bug with QA sign off
    • Create Production Branch Dev lead
  5. Determine a Go or no Go - Product lead
    • If No Go, email team with a formal "stop" notification and a second "go" notification when the process is started again
    • If Go, mention on push bug and email team ahead of time.
      • Make sure an IT lead is assigned to the bug and there is a push time.

Go!

  1. Push to production at assigned time - IT lead
  2. QA verifies production changes - QA Lead
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Execution/Web_Testing/MDN/ReleaseChecklist&oldid=271707"