383
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Release Management/Release Process Checklist Documentation (view source)
Revision as of 15:41, 19 June 2025
, 19 JuneUpdate Android steps related to Samsung Store submissions
No edit summary |
(Update Android steps related to Samsung Store submissions) |
||
| Line 528: | Line 528: | ||
# Turn on managed publishing in the Play Console for Fenix/Focus/Klar. | # Turn on managed publishing in the Play Console for Fenix/Focus/Klar. | ||
# Manually create a Fenix/Focus/Klar release on the Production track with a 5% rollout. | # Manually create a Fenix/Focus/Klar release on the Production track with a 5% rollout. | ||
# Submit the Fenix/Focus/Klar release for review. | # Submit the Fenix/Focus/Klar release for Play Store review. | ||
# Submit the Fenix/Focus release for Samsung Store review with a 5% rollout. | |||
#* Please Note: The submission is automatically created as part of the push. | |||
#* Delete the N-2 version so that only the previous release and RC packages remain. | |||
#* Set to publish manually, the review should complete during RC week. | |||
# Push Desktop to Beta at 100% from Ship-It via Ship RC. | # Push Desktop to Beta at 100% from Ship-It via Ship RC. | ||
#* [[File:Screenshot 2022-06-07 at 09-32-46 RelMan Activities Overview.png|thumb|center]] | #* [[File:Screenshot 2022-06-07 at 09-32-46 RelMan Activities Overview.png|thumb|center]] | ||
| Line 604: | Line 608: | ||
#* Reply to the QA sign-off slack message | #* Reply to the QA sign-off slack message | ||
#** “Thanks, pushed to Production at 5% rolled out. | #** “Thanks, pushed to Production at 5% rolled out. | ||
# | # Publish Fenix/Focus on the Samsung Store. | ||
#* Please note: It can take up to 2 days for review, so it might still be pending. | |||
#* Please note: It can take up to 2 days for review. | |||
==As available, the following should be monitored/performed during RC week for iOS== | ==As available, the following should be monitored/performed during RC week for iOS== | ||
| Line 835: | Line 833: | ||
##* If an app is still pending review on a closed track then you cannot promote it to a production track. | ##* 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. | ##* 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. | ## Submit the Fenix/Focus/Klar release for Play Store review. | ||
##* Keep the same release notes as the major release. Add any new notes at the top prefixed by the dot release version. | ##* 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. | ##* With managed publishing turned on, the app will not automatically release after the store review. | ||
## Submit the Fenix/Focus release for Samsung Store review with a 25% rollout and set to publish automatically | |||
##* This allows the review to go through slightly faster | |||
##* Set the publish time to later in the go-live day. This gives enough time to react if the build fails QA | |||
# Follow the same process as monitoring when an RC build has QA sign-off with the following exceptions: | # 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] in the Play Console. | ## Turn off [https://support.google.com/googleplay/android-developer/answer/9859654?hl=en managed publishing] in the Play Console. | ||