383
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Jump to navigation
Jump to search
Release Management/Release Process Checklist Documentation (view source)
Revision as of 13:12, 11 September 2024
, 11 September 2024Updated the dot release steps to include a section on Android also covering "managed publishing"
(Added a step to update the nighty+ tracking as appropriate) |
(Updated the dot release steps to include a section on Android also covering "managed publishing") |
||
| Line 735: | Line 735: | ||
==The following tasks need to be performed at the start of preparing a dot release== | ==The following tasks need to be performed at the start of preparing a dot release== | ||
'''Desktop''' | |||
# Duplicate the Desktop Dot Release Checklist tab and name it appropriately. | # Duplicate the Desktop Dot Release Checklist tab and name it appropriately. | ||
#* Example: Desktop 101.0.1 | #* Example: Desktop 101.0.1 | ||
# Email release-drivers group to inform them a dot release is being created. #* Include information on the driver, if there will be an Android release, and a link to the sheet used to track the uplifts. | # Email release-drivers group to inform them a dot release is being created. | ||
#* Include information on the driver, if there will be an Android release, and a link to the sheet used to track the uplifts. | |||
#* [https://groups.google.com/a/mozilla.org/g/release-drivers/c/pt_yKRur89I/m/-zTFEiq9AAAJ Example Email] | #* [https://groups.google.com/a/mozilla.org/g/release-drivers/c/pt_yKRur89I/m/-zTFEiq9AAAJ Example Email] | ||
# Review any pending release uplift requests | # Review any pending release uplift requests | ||
| Line 751: | Line 753: | ||
#** Otherwise, request wording before adding the release note. | #** Otherwise, request wording before adding the release note. | ||
# Follow the same process as creating an RC build | # Follow the same process as creating an RC build | ||
#* If any uplifts impact | #* If any uplifts impact Android then duplicate the Android Dot Release Checklist tab and name it appropriately. | ||
# | # Follow the same process as monitoring when an RC build has QA sign-off | ||
# Follow the same process as | |||
'''Android''' | |||
# Duplicate the Android Dot Release Checklist tab and name it appropriately. | |||
#* Example: Android 101.0.1 | |||
# Follow the same process as creating an RC build with the following exceptions: | |||
## Turn on [https://support.google.com/googleplay/android-developer/answer/9859654?hl=en managed publishing] | |||
##* This allows you to submit an app for review but control when it is published. | |||
## Manually create a Fenix/Focus/Klar release on the Production track with a 25% rollout | |||
##* If an app is still pending review on a closed track then you cannot promote it to a production track. | |||
##* See [https://support.google.com/googleplay/android-developer/answer/9859348?hl=en Prepare and roll out a release] for more information. | |||
## Submit the Fenix/Focus/Klar release for review | |||
##* Keep the same release notes as the major release. Add any new notes at the top prefixed by the dot release version. | |||
##* With managed publishing turned on, the app will not automatically release after the store review. | |||
# Follow the same process as monitoring when an RC build has QA sign-off with the following exceptions: | |||
## Turn off [https://support.google.com/googleplay/android-developer/answer/9859654?hl=en managed publishing] | |||
##* With managed publishing turned off, the app will be automatically released after store review. | |||
==The following tasks need to be performed during go-live of a dot release== | ==The following tasks need to be performed during go-live of a dot release== | ||