Confirmed users
14,525
edits
QA/Desktop Firefox/Walkthroughs/Release Coordination: Difference between revisions
Jump to navigation
Jump to search
QA/Desktop Firefox/Walkthroughs/Release Coordination (view source)
Revision as of 22:56, 15 April 2014
, 15 April 2014→Aurora
(→Beta) |
(→Aurora) |
||
| Line 599: | Line 599: | ||
Once the migration happens, the first Beta build will be generated. Testing of this build can begin on Tuesday after the releases have been shipped and must be completed by Thursday. See the Beta section for more details. | Once the migration happens, the first Beta build will be generated. Testing of this build can begin on Tuesday after the releases have been shipped and must be completed by Thursday. See the Beta section for more details. | ||
= Beta = | |||
== Timeline == | |||
* Day 0 (Monday) | |||
** Release Management will migrate mozilla-aurora to mozilla-beta | |||
** Automation Development migrates the mozmill-tests mozilla-aurora branch to mozilla-beta | |||
* Day 1 (Tuesday) | |||
** Release Management will send the go-to-build for the first Beta | |||
** Release Engineering will generate the builds (takes several hours) | |||
** QA develops a test plan including manual regression tests and bug fix verifications, then coordinates overnight testing of the Beta candidates via email to Softvision | |||
* Day 2 (Wednesday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''betatest'' channel, and update automation on the ''releasetest'' channel | |||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | |||
* Day 3 (Thursday) | |||
** QA signs off the Beta candidate for release to beta testers via email to Release Drivers | |||
** Release Management sends email to push the Beta updates live | |||
** Release Engineering pushes the updates live and sends an email to Release Drivers when complete | |||
** QA runs Mozmill-Ondemand update automation on the ''beta'' channel and sends a sign-off email to Release Drivers when complete | |||
* Day 4..7 | |||
** QA continues feature testing, dogfooding, and QAWANTED bug investigations, providing status updates of top issues in the Tuesday & Thursday Release Coordination meeting | |||
* Day 8 (Tuesday) | |||
** Release Management will send the go-to-build for the second Beta | |||
** Release Engineering will generate the builds (takes several hours) | |||
** QA develops a test plan including manual regression tests and bug fix verifications, then coordinates overnight testing of the Beta candidates via email to Softvision | |||
* Day 9 (Wednesday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''betatest'' channel, and update automation on the ''releasetest'' channel | |||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | |||
* Day 10 (Thursday) | |||
** QA signs off the Beta candidate for release to beta testers via email to Release Drivers | |||
** Release Management sends email to push the Beta updates live | |||
** Release Engineering pushes the updates live and sends an email to Release Drivers when complete | |||
** QA runs Mozmill-Ondemand update automation on the ''beta'' channel and sends a sign-off email to Release Drivers when complete | |||
* Day 11..14 | |||
** QA continues feature testing, dogfooding, and QAWANTED bug investigations, providing status updates of top issues in the Tuesday & Thursday Release Coordination meeting | |||
* Day 15 (Tuesday) | |||
** Release Management will send the go-to-build for the third Beta | |||
** Release Engineering will generate the builds (takes several hours) | |||
** QA develops a test plan including manual regression tests and bug fix verifications, then coordinates overnight testing of the Beta candidates via email to Softvision | |||
* Day 16 (Wednesday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''betatest'' channel, and update automation on the ''releasetest'' channel | |||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | |||
* Day 17 (Thursday) | |||
** QA signs off the Beta candidate for release to beta testers via email to Release Drivers | |||
** Release Management sends email to push the Beta updates live | |||
** Release Engineering pushes the updates live and sends an email to Release Drivers when complete | |||
** QA runs Mozmill-Ondemand update automation on the ''beta'' channel and sends a sign-off email to Release Drivers when complete | |||
* Day 18..21 | |||
** QA continues feature testing, dogfooding, and QAWANTED bug investigations, providing status updates of top issues in the Tuesday & Thursday Release Coordination meeting | |||
* Day 22 (Tuesday) | |||
** Release Management will send the go-to-build for the fourth Beta | |||
** Release Engineering will generate the builds (takes several hours) | |||
** QA develops a test plan including manual regression tests and bug fix verifications, then coordinates overnight testing of the Beta candidates via email to Softvision | |||
* Day 23 (Wednesday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''betatest'' channel, and update automation on the ''releasetest'' channel | |||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | |||
* Day 24 (Thursday) | |||
** QA signs off the Beta candidate for release to beta testers via email to Release Drivers | |||
** Release Management sends email to push the Beta updates live | |||
** Release Engineering pushes the updates live and sends an email to Release Drivers when complete | |||
** QA runs Mozmill-Ondemand update automation on the ''beta'' channel and sends a sign-off email to Release Drivers when complete | |||
* Day 25..28 | |||
** QA continues feature testing, dogfooding, and QAWANTED bug investigations, providing status updates of top issues in the Tuesday & Thursday Release Coordination meeting | |||
* Day 29 (Tuesday) | |||
** Release Management will send the go-to-build for the fifth Beta | |||
** Release Engineering will generate the builds (takes several hours) | |||
** QA develops a test plan including manual regression tests and bug fix verifications, then coordinates overnight testing of the Beta candidates via email to Softvision | |||
* Day 30 (Wednesday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''betatest'' channel, and update automation on the ''releasetest'' channel | |||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | |||
* Day 31 (Thursday) | |||
** QA signs off the Beta candidate for release to beta testers via email to Release Drivers | |||
** Release Management sends email to push the Beta updates live | |||
** Release Engineering pushes the updates live and sends an email to Release Drivers when complete | |||
** QA runs Mozmill-Ondemand update automation on the ''beta'' channel and sends a sign-off email to Release Drivers when complete | |||
* Day 32..35 (Monday) | |||
** Release Management will send the go-to-build for the final Beta | |||
** Release Engineering will generate the builds (takes several hours) | |||
** QA develops a test plan including manual regression tests and bug fix verifications, then coordinates overnight testing of the Beta candidates via email to Softvision | |||
* Day 36 (Tuesday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''betatest'' channel, and update automation on the ''releasetest'' channel | |||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | |||
** Release Management migrates mozilla-beta to mozilla-release and sends the go to build the first release candidate | |||
* Day 37 (Wednesday) | |||
** QA signs off the Beta candidate for release to beta testers via email to Release Drivers | |||
** Release Management sends email to push the Beta updates live | |||
** Release Engineering pushes the updates live and sends an email to Release Drivers when complete | |||
** QA runs Mozmill-Ondemand update automation on the ''beta'' channel and sends a sign-off email to Release Drivers when complete | |||
* Day 42 (Monday) | |||
** Release Management migrates mozilla-aurora to mozilla-beta | |||
== Priorities == | |||