QA/Execution/Web Testing/MDN/ReleaseChecklist: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
(→Get Set: Adding calendar, string freeze) |
||
| Line 14: | Line 14: | ||
# File push bug in mozilla.org/Server Operations - Web Content Push - <font color="blue">Dev lead</font> | # File push bug in mozilla.org/Server Operations - Web Content Push - <font color="blue">Dev lead</font> | ||
#* Offer a date and time to IT - <font color="blue">Dev lead</font> | #* Offer a date and time to IT - <font color="blue">Dev lead</font> | ||
#* Add deployment time to [[Webdev:Releases]] calendar | |||
# Extract strings | |||
# Enact a code freeze - <font color="brown">Dev lead</font> | # Enact a code freeze - <font color="brown">Dev lead</font> | ||
#* Email team with notification | #* Email team with notification | ||
#* Email l10n <font color="blue">Product lead</font> | |||
# Staging verification - <font color="orange">QA Lead</font> | # Staging verification - <font color="orange">QA Lead</font> | ||
#* QA performs release testing | #* QA performs release testing | ||
#* When signed off, email team with notification | #* When signed off, email team with notification | ||
#* Update push bug with QA sign off | #* Update push bug with QA sign off | ||
#* Create Production Branch <font color="brown">Dev lead</font> | |||
# Determine a Go or no Go - <font color="blue">Product lead</font> | # Determine a Go or no Go - <font color="blue">Product lead</font> | ||
#* If '''No Go''', email team with a formal "stop" notification and a second "go" notification when the process is started again | #* If '''No Go''', email team with a formal "stop" notification and a second "go" notification when the process is started again | ||
Revision as of 18:00, 3 December 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/QA 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
- Add deployment time to Webdev:Releases calendar
- Extract strings
- Enact a code freeze - Dev lead
- Email team with notification
- Email l10n Product lead
- Staging verification - QA Lead
- QA performs release testing
- When signed off, email team with notification
- Update push bug with QA sign off
- Create Production Branch Dev lead
- 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