Release Management/Release Process Checklist Documentation: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 352: Line 352:
#** Verify that the Background rate for Devedition-xx.0b1-buildx is 100.
#** Verify that the Background rate for Devedition-xx.0b1-buildx is 100.
# Ensure the Firefox iOS build is available in Testflight
# Ensure the Firefox iOS build is available in Testflight
#* [https://appstoreconnect.apple.com/apps/1073219424/testflight Firefox Beta TestFlight]
#* If the build is not pushed then check the build status in the [https://app.bitrise.io/app/6c06d3a40422d10f?workflow=workflow-SPM_Deploy_Prod_Beta BitRise pipeline]  
#* If the build is not pushed then check the build status in the [https://app.bitrise.io/app/6c06d3a40422d10f?workflow=workflow-SPM_Deploy_Prod_Beta BitRise pipeline]  
# Monitor for QA sign-off on Desktop and DevEdition build validation for both update/functional testing.
# Monitor for QA sign-off on Desktop and DevEdition build validation for both update/functional testing.
Line 412: Line 413:
Once a release moves to the Release cycle, preparations for the release candidates begin. Until go-live, the daily tasks are similar to the beta cycle in terms of monitoring and if needed create a new release candidate.
Once a release moves to the Release cycle, preparations for the release candidates begin. Until go-live, the daily tasks are similar to the beta cycle in terms of monitoring and if needed create a new release candidate.


==The following tasks need to be performed at the start of RC week (week before go-live)==
==The following tasks need to be performed at the start of RC week (week before go-live) for Desktop/Android ==
# Review tracking-firefoxXXX+ bugs and approval requests
# Review tracking-firefoxXXX+ bugs and approval requests
#* Verify that all approved uplift requests were uplifted to beta
#* Verify that all approved uplift requests were uplifted to beta
Line 439: Line 440:
# Bump Firefox Android version number from XXX.0bX to X.0.0
# Bump Firefox Android version number from XXX.0bX to X.0.0
#* See [https://github.com/mozilla-mobile/firefox-android/commit/0d78c43f16fda39b5ac39b9ac5eea1d8a1e793a9 Example]
#* See [https://github.com/mozilla-mobile/firefox-android/commit/0d78c43f16fda39b5ac39b9ac5eea1d8a1e793a9 Example]
# Create Firefox Android GV bump PR and change track if necessary.
# Change the Firefox Android GeckoChannel from BETA to RELEASE
## Fork the release branch.
#* See [https://github.com/mozilla-mobile/firefox-android/commit/86a771014d5a4515c7ec87d22257f8eb99fa7073 Example]
## Change and commit the following:
# Confirm GV bump PR is merged to the firefox-android releases_vXXX branch
##* android-components/plugins/dependencies/src/main/java/Gecko.kt
#* Check the status of the PR pending automatically created when a new GeckoView is available in Maven.
##** Change the GeckoView Version to the RC1 GeckoView package.
##*** Please Note: The package number for RC1 can be found in [https://maven.mozilla.org/?prefix=maven2/org/mozilla/geckoview/geckoview/ Maven]
##** Change the GeckoChannel from beta to release.
##*** From ''val channel = GeckoChannel.BETA'' to ''val channel = GeckoChannel.RELEASE''
## Create a PR to merge the fork into the release branch and request review from another release management team member.
##* See [https://github.com/mozilla-mobile/firefox-android/pull/518 Example]
## Once the PR is approved and the CI tests pass, merge the PR.
# Check if there are any pending PRs for firefox-android release branch before proceeding with the steps to build Fenix/Focus.
# Check if there are any pending PRs for firefox-android release branch before proceeding with the steps to build Fenix/Focus.
#* [https://github.com/mozilla-mobile/firefox-android/pulls firefox-android]
#* [https://github.com/mozilla-mobile/firefox-android/pulls firefox-android]
Line 485: Line 479:
## Submit to the store for review
## Submit to the store for review
#* Please see [https://docs.microsoft.com/en-us/windows/uwp/publish/app-submissions App submissions] documentation for additional information on the Microsoft Store submission process.
#* Please see [https://docs.microsoft.com/en-us/windows/uwp/publish/app-submissions App submissions] documentation for additional information on the Microsoft Store submission process.
==The following tasks need to be performed at the start of RC week (week before go-live) for iOS ==
'''Focus iOS'''
# Check if there are any pending PRs for the focus-ios release branch.
#* [https://github.com/mozilla-mobile/focus-ios/pulls focus-ios]
#* Example Filter: ''is:pr is:open base: releases_v115''
# Tag the release in GitHub.
#* [https://github.com/mozilla-mobile/focus-ios/releases/tag/v115.0 Example Release]
#* Set as a pre-release.
# Verify the Focus/Klar release is available in TestFlight.
#* [https://appstoreconnect.apple.com/apps/1055677337/testflight Firefox Focus TestFlight]
#* https://appstoreconnect.apple.com/apps/1073435754/testflight Firefox Klar TestFlight]
'''Firefox iOS'''
# Check if there are any missing backports from the previous release.
#* Ensure that any backports from the dot releases on the previous version were also backported.
# Check if there are any pending PRs for the firefox-ios release branch.
#* [https://github.com/mozilla-mobile/firefox-ios/pulls firefox-ios]
#* Example Filter: ''is:pr is:open base:release/v115''
# Sync with the iOS team for Hard Freeze.
#* Ask on [https://mozilla.slack.com/archives/C03PKCHHSSD #firefox-ios-releases] Slack channel
#* See [https://mozilla.slack.com/archives/C03PKCHHSSD/p1687795018726399 Example]
# Run the strings sync action.
# See documentation [https://github.com/mozilla-mobile/firefox-ios/wiki/Localization-Process#github-action-import-process here].
# Trigger the firefox-ios SPM_Deploy_Prod_Beta bitrise build workflow for the release branch.
# Verify that Firefox iOS release is available in TestFlight.
#* [https://appstoreconnect.apple.com/apps/989804926/testflight Firefox TestFlight]
# Update PI request if there have been any changes since the last QA signoff.


==As available, the following should be monitored/performed during RC week==
==As available, the following should be monitored/performed during RC week==
273

edits