Release Management/Release Process Checklist Documentation: Difference between revisions

Jump to navigation Jump to search
Updated the Android related steps in the rc checklist
No edit summary
(Updated the Android related steps in the rc checklist)
Line 442: Line 442:
# Confirm Desktop build has started.
# Confirm Desktop build has started.
#* Taskcluster email: “[desktop] Build of firefox xx.0 build 1”
#* Taskcluster email: “[desktop] Build of firefox xx.0 build 1”
# Bump Firefox Android version number from XXX.0bX to X.0.0
#* See [https://github.com/mozilla-mobile/firefox-android/commit/463f201b4d2baf1d0a0bdb0f1868ae70e0d4a263 Example]
# Change the Firefox Android GeckoChannel from BETA to RELEASE
#* See [https://github.com/mozilla-mobile/firefox-android/commit/86a771014d5a4515c7ec87d22257f8eb99fa7073 Example]
# Confirm GV bump PR is merged to the firefox-android releases_vXXX branch
#* Check the status of the PR pending automatically created when a new GeckoView is available in Maven.
# 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]
#* Example Filter: ''is:pr is:open base: releases_v101.0''
#* If the pending PR is reviewed and is waiting on CI, then where possible wait until the PR has been merged.
#* If ever unsure, reach out on the android team Slack channel [https://mozilla.slack.com/archives/C016PEDKY90 #mobile-android-team]
# Set up Firefox Android (AC, Fenix, Focus) release in Ship-It.
# Set up Firefox Android (AC, Fenix, Focus) release in Ship-It.
#* Follow the same steps as creating a beta build.
#* Follow the same steps as creating a beta build.
273

edits

Navigation menu