QA/Execution/Web Testing/MDN/ReleaseChecklist: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
(→Go!) |
|||
| Line 29: | Line 29: | ||
# 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> | ||
Revision as of 19:49, 16 November 2010
Team
- Product lead: Jay Patel
- Dev lead: Ozten King/Craig Cook
- QA lead: Raymond
- IT lead: push bug assignee
Get Ready
- Decision on release date and features - Product/Dev Lead
- Triage of blocking/approval requests as needed - Product/Dev Lead
- Update staging data from prod if necessary.
Get Set
- File push bug in mozilla.org/Server Operations - Web Content Push - Dev lead
- Offer a date and time to IT - Dev lead
- Enact a code freeze - Dev lead
- Email team with notification
- Staging verification - QA Lead
- QA performs release testing
- When signed off, email team with notification
- Update push bug with QA sign off
- 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!
- Push to production at assigned time - IT lead
- QA verifies production changes - QA Lead