383
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Release Management/Release Process Checklist Documentation (view source)
Revision as of 18:14, 1 August 2023
, 1 August 2023no edit summary
No edit summary |
No edit summary |
||
| Line 191: | Line 191: | ||
#* The Firefox Android (Android-Components, Fenix, Focus) release branch is used for beta and rc builds. This step can be performed before the Beta 1 build has shipped to the beta channel, geckoview is built during the desktop promote phase. | #* The Firefox Android (Android-Components, Fenix, Focus) release branch is used for beta and rc builds. This step can be performed before the Beta 1 build has shipped to the beta channel, geckoview is built during the desktop promote phase. | ||
# Perform the release management steps in the [https://github.com/mozilla-mobile/firefox-ios/wiki/Release-Checklist#soft-freeze-tasks Firefox iOS Soft Freeze Checklist] | # Perform the release management steps in the [https://github.com/mozilla-mobile/firefox-ios/wiki/Release-Checklist#soft-freeze-tasks Firefox iOS Soft Freeze Checklist] | ||
# Branch focus-ios from main to releases_vxxx | |||
#* Create a branch name with the format releases_v[beta_version] off of the [https://github.com/mozilla-mobile/focus-ios main branch] (for example, releases_v109) through the GitHub UI. [beta_version] should follow the Firefox Beta release number. | |||
# Bump the version by running [https://github.com/mozilla-mobile/focus-ios/blob/main/tools/set-version.sh set-version.sh script] in the releases_v[beta_version] branch of focus-ios | |||
# Pin the AS version in the focus-ios release branch | |||
#* See [https://github.com/mozilla-mobile/focus-ios/pull/3804 Example PR] | |||
# Review any pending uplifts that may be required before proceeding with a beta 1 build | # Review any pending uplifts that may be required before proceeding with a beta 1 build | ||
#* This should not be a common occurrence, however, an example would be a crash fix that may have landed in central post-merge. | #* This should not be a common occurrence, however, an example would be a crash fix that may have landed in central post-merge. | ||
| Line 222: | Line 227: | ||
#* Taskcluser email: “firefox xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | #* Taskcluser email: “firefox xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | ||
#* Taskcluser email: “devedition xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | #* Taskcluser email: “devedition xxx.0b1 build1/mozilla-beta has been pushed to cdntest” | ||
# Confirm GV bump PR is merged to the firefox-android releases_vXXX branch | # Confirm GV bump PR is merged to the firefox-android releases_vXXX branch | ||
#* The GeckoView build is created during the promote phase of the desktop build | #* The GeckoView build is created during the promote phase of the desktop build | ||