QA/Execution/Web Testing/SUMO/Release Checklist
< QA | Execution | Web Testing | SUMO
Jump to navigation
Jump to search
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
- 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
- Update Releases/PRODUCT&VERSION with proposed schedule - Project lead
- Email dev-planning and release-drivers with proposed schedule - Project lead
- Triage of blocking/approval requests as needed - Entire team (minus build)
- Schedule meetings - Project lead
- Alert developers of blockers - QA lead
- Alert developers of upcoming freeze - Dev lead
- Development code freeze - Dev lead
- Hand off to QA for verifications - QA Lead
- Dev lead tags the tree - Dev lead
- 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