QA/Execution/Web Testing/MDN/ReleaseChecklist

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
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