QA/Execution/Web Testing/SUMO/Release Checklist

This is the general release checklist we should use.

It is organized by major functional activity in roughly chronological order. At the end of each bullet is the owner of the checklist item.

Team

• Project lead: David Tenser
• Dev lead: James Socol
• QA lead: Stephen Donner/Vishal Kamdar
• IT lead: Shayam Mani/Trevor Hardcastle

Checklist

First things first

• Meet and schedule release - Entire SUMO dev team
• Decision on release date - Entire team
  • Update SUMO Meeting Notepad page with correct milestones and target freeze/push dates - Dev lead
  • Email sumo-dev@mozilla.com with proposed schedule - Dev lead

• Triage of blocking/approval requests as needed - Dev lead
  • Schedule meetings - Project lead
  • Alert developers of upcoming freeze - Dev lead

Development Phase

• Development code freeze - Dev lead
  • Hand off to QA for verifications - QA Lead
  • Alert developers of blockers - QA lead

Development finished, code frozen

• Dev lead tags the tree - Dev lead
• Dev lead files the IT push bug - Dev lead

QA phase

• QA tests builds - QA Lead (usually and should happen(s) before tree is tagged)
• QA runs ad-hoc and Litmus tests, and individual bug verifications for that milestone
  • When signed off, email sumo-dev@mozilla.com with notification - QA Lead

Push day

• Team is notified via IT push bug or IRC in #sumodev of the push time - IT lead
• IT pushes at the agreed-upon time and updates the bug and #sumodev channel of the changes
• Dev/QA/IT agree it's stable to test - Entire SUMO dev team + IT
• QA begins testing fixed bugs and running a combination of Litmus tests + automation (eventually -- not there yet w/Kitsune) - QA Lead
• Once QA (and everyone) feels comfortable with the build, they verify the push bug - QA Lead