Confirmed users
14,525
edits
QA/Desktop Firefox/Walkthroughs/Release Coordination: Difference between revisions
QA/Desktop Firefox/Walkthroughs/Release Coordination (view source)
Revision as of 22:58, 15 April 2014
, 15 April 2014→Beta
(→Beta) |
|||
| Line 655: | Line 655: | ||
channel and everything is working as expected. | channel and everything is working as expected. | ||
</pre> | </pre> | ||
= Release = | |||
== Timeline == | |||
* Day 0 (Tuesday) | |||
** Release Management migrates the mozilla-beta branch to mozilla-release | |||
** Automation Development migrates the mozmill-tests mozilla-beta branch to mozilla-release | |||
** Release Management sends the go-to-build for the first Release Candidate | |||
** Release Engineering generates the builds (takes several hours) | |||
* Day 1 (Wednesday) | |||
** QA develops a Release test plan including manual regression tests and bug fix verifications, then coordinates overnight testing of the Release Candidates via email to Softvision | |||
* Day 2 (Thursday) | |||
** QA runs Mozmill-Ondemand functional automation, update automation on the ''betatest'' channel | |||
** QA coordinates further overnight testing of the Release Candidates via email to Softvision | |||
* Day 3 (Friday) | |||
** QA coordinates further overnight testing of the Release Candidates via email to Softvision | |||
* Day 6 (Monday) | |||
** QA sends conditional sign-off of the Release Candidates via email to the Release Drivers | |||
** Release Management sends the go to push snippets to mirrors | |||
** Release Engineering pushes Release Candidate snippets to mirrors and sends email to Release Drivers when complete | |||
** QA runs Mozmill-Ondemand update automation on the ''releasetest'' channel | |||
* Day 7 (Tuesday) | |||
** QA sends final sign-off for release via email to the Release Drivers | |||
** Release Management sends the go to push snippets live | |||
** Release Engineering pushes Release Candidate snippets live and sends email to the Release Drivers when complete | |||
** QA runs Mozmill-ondemand update automation on the ''release'' channel then sends a sign-off email to Release Drivers when complete | |||
** Release Management pushes web content | |||
** WebQA verifies web content is live | |||
** RRRT creates a page to track potential .point release issues | |||
* Day 8+ | |||
** QA assists with investigating any potential point release issues and prepares test plans for point releases as required | |||
* Day 41 (Monday) | |||
** Point of no return for any point releases | |||
* Day 42 (Tuesday) | |||
** Release Management migrates mozilla-beta to mozilla-release and sends the go to build the next Release | |||