QA/Execution/Web Testing/MDN/ReleaseChecklist: Difference between revisions

→‎Get Set: Adding calendar, string freeze
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
Confirmed users
1,136

edits