Confirmed users
1,017
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Jump to navigation
Jump to search
m
Release Management/Release Process Checklist Documentation (view source)
Revision as of 17:02, 22 May 2019
, 22 May 2019→RC Checklist
m (update wording) |
m (→RC Checklist) |
||
| Line 114: | Line 114: | ||
** Sample partials (for 66.0 RC): 65.0.2build1,65.0.1build2,65.0build2,64.0.2build1,66.0b14build1 | ** Sample partials (for 66.0 RC): 65.0.2build1,65.0.1build2,65.0build2,64.0.2build1,66.0b14build1 | ||
* '''Update test on beta-cdntest; QA will email release-signoff to push Desktop to Beta at 100%.''' Relman can then click "push RC" in ship-it. (RC builds can be pushed to Beta users once they receive sign-off from QA.) The ''beta'' and ''beta-cdntest'' channels download RC builds from the `candidates` directory, so this happens prior to pushing to ''releases'' (aka CDNs). Pushing to release users is covered by the Go-Live Checklist elsewhere. | * '''Update test on beta-cdntest; QA will email release-signoff to push Desktop to Beta at 100%.''' Relman can then click "push RC" in ship-it. (RC builds can be pushed to Beta users once they receive sign-off from QA.) The ''beta'' and ''beta-cdntest'' channels download RC builds from the `candidates` directory, so this happens prior to pushing to ''releases'' (aka CDNs). Pushing to release users is covered by the Go-Live Checklist elsewhere. | ||
* '''Verify rollout % of current release.''' If the current latest version is on a staged rollout, pushing a newer release to the Play Store with a 5% staged rollout will overwrite the previous staged rollout and the fallback version may not be the expected one. This step is to verify that users not getting the 5% RC rollout will still get the latest stable release instead. | * '''Verify rollout % of current release in Play Store.''' If the current latest version is on a staged rollout, pushing a newer release to the Play Store with a 5% staged rollout will overwrite the previous staged rollout and the fallback version may not be the expected one. This step is to verify that users not getting the 5% RC rollout will still get the latest stable release instead. | ||
* '''Push to Play Store at 5%.''' Because of how the Play Store works, we are unable to ship Fennec RC builds to Beta users prior to release like we do for Desktop Firefox builds. In order to get pre-release testing coverage, Fennec RC builds are therefore pushed '''release''' users on the Play Store at 5% once they receive QA sign-off. | * '''Push to Play Store at 5%.''' Because of how the Play Store works, we are unable to ship Fennec RC builds to Beta users prior to release like we do for Desktop Firefox builds. In order to get pre-release testing coverage, Fennec RC builds are therefore pushed '''release''' users on the Play Store at 5% once they receive QA sign-off. | ||
* '''WNP testing on release-localtest.''' RC week is when testing of the What’s New Page for the new release commences. This is done on the release-localtest channel by QA and a sign-off email will be sent once testing has been completed. It’s not necessary for every RC build to go through this testing as long as there has been a successful sign-off by the end of RC week. | * '''WNP testing on release-localtest.''' RC week is when testing of the What’s New Page for the new release commences. This is done on the release-localtest channel by QA and a sign-off email will be sent once testing has been completed. It’s not necessary for every RC build to go through this testing as long as there has been a successful sign-off by the end of RC week. | ||