Confirmed users
2,822
edits
QA/Desktop Firefox/Walkthroughs/Release Coordination: Difference between revisions
Jump to navigation
Jump to search
m
QA/Desktop Firefox/Walkthroughs/Release Coordination (view source)
Revision as of 15:10, 24 October 2014
, 24 October 2014→Timeline: removed "run functional automation" from the walkthrough since now functional testing kicks off automatically for all locales
m (→Beta: more fixes to the schedule) |
m (→Timeline: removed "run functional automation" from the walkthrough since now functional testing kicks off automatically for all locales) |
||
| Line 95: | Line 95: | ||
*After go-to-build, it is about 3.5 hours until linux builds out, 5 hours for all en-US builds, 7 hours for all builds, 7.5 hours for updates on beta-localtest. | *After go-to-build, it is about 3.5 hours until linux builds out, 5 hours for all en-US builds, 7 hours for all builds, 7.5 hours for updates on beta-localtest. | ||
* No need to run ondemand functional tests any more as of Oct. 2014. All locales are covered in the automated tests that run overnight. | |||
*Mozmill tests run on builds on several channels. | *Mozmill tests run on builds on several channels. | ||
| Line 109: | Line 110: | ||
** 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. | ** 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) | * Day 2 (Wednesday) | ||
** functional tests can start as soon as 'Updates available on beta-localtest' email comes in. That indicates all the builds are done. | ** functional tests can start as soon as 'Updates available on beta-localtest' email comes in. That indicates all the builds are done. (This is obsolete) | ||
** QA runs Mozmill ondemand update tests on the''beta-cdntest'' channel. | ** QA runs Mozmill ondemand update tests on the''beta-cdntest'' channel. | ||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | ** QA coordinates further overnight testing of the Beta candidates via email to Softvision | ||
| Line 133: | Line 134: | ||
** QA coordinates further overnight testing of the Beta candidates via email to Softvision | ** QA coordinates further overnight testing of the Beta candidates via email to Softvision | ||
* Day 11 (Friday) | * Day 11 (Friday) | ||
** QA runs Mozmill-Ondemand | ** QA runs Mozmill-Ondemand update automation on the ''beta-localtest'' and ''beta-cdntest'' channels. | ||
** QA signs off the Beta candidate for release to beta testers via email to release-drivers | ** 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 Management sends email to push the Beta updates live | ||
| Line 146: | Line 147: | ||
** 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 | ** 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) | * Day 16 (Wednesday) | ||
** QA runs Mozmill-Ondemand | ** QA runs Mozmill-Ondemand 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 | ** QA coordinates further overnight testing of the Beta candidates via email to Softvision | ||
* Day 17 (Thursday) | * Day 17 (Thursday) | ||
| Line 160: | Line 161: | ||
** 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 | ** 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) | * Day 23 (Wednesday) | ||
** QA runs Mozmill-Ondemand | ** QA runs Mozmill-Ondemand 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 | ** QA coordinates further overnight testing of the Beta candidates via email to Softvision | ||
* Day 24 (Thursday) | * Day 24 (Thursday) | ||
| Line 174: | Line 175: | ||
** 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 | ** 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) | * Day 30 (Wednesday) | ||
** QA runs Mozmill-Ondemand | ** QA runs Mozmill-Ondemand 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 | ** QA coordinates further overnight testing of the Beta candidates via email to Softvision | ||
* Day 31 (Thursday) | * Day 31 (Thursday) | ||
| Line 186: | Line 187: | ||
** 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 | ** 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) | * Day 36 (Tuesday) | ||
** QA runs Mozmill-Ondemand | ** QA runs Mozmill-Ondemand 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 | ** 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 | ** Release Management migrates mozilla-beta to mozilla-release and sends the go to build the first release candidate | ||