QA/Execution/Web Testing/MDN/ReleaseChecklist

From MozillaWiki
< QA‎ | Execution‎ | Web Testing
Revision as of 19:46, 16 November 2010 by Retornam (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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
  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
  2. Enact a code freeze - Dev lead
    • Email team with notification
  3. Staging verification - QA Lead
    • QA performs release testing
    • When signed off, email team with notification
    • Update push bug with QA sign off
    • Confirm release notes with Dev lead, QA lead, others as appropriate
  4. 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.
      • Tag the branch for release with the appropriate version - Dev lead

Go!

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