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 22:44, 22 October 2014
, 22 October 2014→Beta: more fixes to the schedule
m (→Timeline: minor format fixes) |
m (→Beta: more fixes to the schedule) |
||
| Line 90: | Line 90: | ||
== Timeline == | == Timeline == | ||
General notes: | |||
*Check mozmill configuration files with http://www.mozqa.com/mciconf/app/ before uploading them. | |||
*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. | |||
*Mozmill tests run on builds on several channels. | |||
** beta-localtest tests updates on our ftp server. | |||
** beta-cdntest hits the CDN. (We only need to run one, preferably cdntest) | |||
** beta also tests the update builds on our CDN. | |||
* Day 0 (Monday) | * Day 0 (Monday) | ||
| Line 96: | Line 105: | ||
** Automation Development migrates the mozmill-tests mozilla-aurora branch to mozilla-beta | ** Automation Development migrates the mozmill-tests mozilla-aurora branch to mozilla-beta | ||
* Day 1 (Tuesday) | * Day 1 (Tuesday) | ||
** Release Management will send the go-to-build for the first Beta | ** Release Management will send the go-to-build email for the first Beta | ||
** Release Engineering | ** Release Engineering generates the builds (takes several hours; overnight) | ||
** 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' comes in. That indicates all the builds are done. | ** 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 | ||
* Day 3 (Thursday) | * Day 3 (Thursday) | ||
| Line 115: | Line 124: | ||
** 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 8 (Tuesday) | * Day 8 (Tuesday) | ||
** QA runs Mozmill-Ondemand functional automation, update automation on the | ** QA runs Mozmill-Ondemand functional automation, then update automation on the ''beta-cdntest'' channel. Report back on this to release-drivers. | ||
** Release Management sends email to push the Beta updates live | ** Release Management sends email to push the Beta updates live | ||
** QA then runs update tests on the ''beta'' channel and reports back to release-drivers. | ** QA then runs update tests on the ''beta'' channel and reports back to release-drivers. | ||