QA/Execution/Web Testing/SUMO/Release Checklist: Difference between revisions

QA/Execution/Web Testing/SUMO/Release Checklist (view source)

535 bytes added , 29 November 2010

no edit summary

Confirmed users

1,504

edits

@@ Line 38: / Line 38: @@
 ** Cache-clearing instructions (if any)
 * IT/Dev updates https://wiki.mozilla.org/Releases with the release date
+* Determine release manager, typically the project manager or lead developer. This person will make calls as to whether to rollback.
+* Prior to the release team meets to discuss:
+** Steps for deployment will be talked through and docs checked
+** Roll back plan will be discussed
+** Rollback decision points will be reviewed
+** Downtime notice plans
 '''Push day'''
 * Team is notified via IT push bug of the push time - <font color="orange">IT lead</font>
+* All team members who are responsible for code or infrastructure affected by the release will be present, or the release will not go ahead. - <strong>Entire SUMO dev team + IT</strong>
 * 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 - <strong>Entire SUMO dev team + IT</strong>
 * QA begins testing fixed bugs and running a combination of Litmus tests + automation (eventually -- not there yet w/Kitsune) - <font color="green">QA lead</font>
 * Once QA (and everyone) feels comfortable with the build, they verify the push bug - <font color="green">QA lead</font>