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 19:10, 2 October 2024

450 bytes added ,  2 October 2024
Updated to reflect the merge steps handled by relman
No edit summary
(Updated to reflect the merge steps handled by relman)
Line 163: Line 163:
#* Remind developers that the window for landing riskier fixes is coming to a close until after the version bump.
#* Remind developers that the window for landing riskier fixes is coming to a close until after the version bump.
#* [https://groups.google.com/a/mozilla.org/g/dev-platform/c/uoCFNyGJx0c Example email]  
#* [https://groups.google.com/a/mozilla.org/g/dev-platform/c/uoCFNyGJx0c Example email]  
# Sync with RelEng to confirm the RelEng on duty for the Central to Beta merge.
#* Sync on Friday before Merge Day
#* Use the [https://matrix.to/#/#releaseduty:mozilla.org #releaseduty] channel on Matrix.
#* Align to perform the merge early on Merge Day, for example, 9/10am ET.
# Sync with the Sheriff team to confirm Central is in a good state so that the Merge Day email can be sent.
#* Sync on Merge Day morning
#* Use the [https://chat.mozilla.org/#/room/#sheriffs:mozilla.org #sheriffs] channel on Matrix.
#* Check the Beta simulations document for the release, this document is emailed to Release Management at the start of the night cycle.
#* Ensure that central does not currently have any known severe regressions or performance issues that would be carried into beta.
# Once you have confirmed central is in a good state, send the Merge Day email to release-drivers and release signoff
#* [https://groups.google.com/a/mozilla.org/g/release-drivers/c/FACrkr1Qgpo Example email] for the merge day of 103:
# Sync with RelEng on the Central to Beta merge
#* Use the [https://matrix.to/#/#releaseduty:mozilla.org #releaseduty] channel on Matrix to mention the merge day email was sent
#* Sync with the RelEng on duty. The RelEng on duty is listed in the Matrix channel description
# Create a Desktop Beta Checklist and Mobile Beta Checklist for beta 1
#* Use the b1 macro
# Wait for RelEng to complete the central to beta merge.
#* Use the [https://matrix.to/#/#releaseduty:mozilla.org #releaseduty] channel on Matrix to synchronize if needed.
#* RelEng will also reply to the Merge Day email
# Prepare the Beta release notes in [https://nucleus.mozilla.org/ Nucleus]
# Prepare the Beta release notes in [https://nucleus.mozilla.org/ Nucleus]
## Click '''Admin Interface'''
## Click '''Admin Interface'''
Line 195: Line 176:
## Set the Release Date to the date when the first Beta is released
## Set the Release Date to the date when the first Beta is released
## Ensure to remove any notes that are only applicable to nightly
## Ensure to remove any notes that are only applicable to nightly
# Sync with RelEng to confirm the RelEng on duty for the Central to Beta merge.
#* Sync on Friday before Merge Day
#* Use the [https://matrix.to/#/#releaseduty:mozilla.org #releaseduty] channel on Matrix.
#* Align they are available for support if needed.
# Sync with AppServices team to confirm who will create the new Swift release on Monday
#* Sync on Friday before Merge Day
#* Use the [https://mozilla.enterprise.slack.com/archives/C0559DDDPQF #application-services-eng] channel on Slack.
# Create checklist(s) for the new ESR cycle
#* Create a checklist for the relevant ESR that corresponds to the Firefox mainline release
#* See [https://whattrainisitnow.com/release/?version=esr ESR calendar]
# Perform the mozilla-central->mozilla-beta no-op trial run
#* See [https://moz-releng-docs.readthedocs.io/en/latest/how-to/releaseduty/merge-duty/merge_duty.html#do-migration-no-op-trial-runs #do-migration-no-op-trial-runs] for documentation.
# Create a Desktop Beta Checklist and Mobile Beta Checklist for beta 1
#* Use the b1 macro


= Beta Checklist =
= Beta Checklist =
Line 201: Line 197:


==The following tasks need to be performed on Merge Day at the start of the Beta cycle after the merge to beta is finished==
==The following tasks need to be performed on Merge Day at the start of the Beta cycle after the merge to beta is finished==
# Sync with the Sheriff team to confirm Central is in a good state so that the Merge Day email can be sent.
#* Sync on Merge Day morning
#* Use the [https://chat.mozilla.org/#/room/#sheriffs:mozilla.org #sheriffs] channel on Matrix.
#* Check the Beta simulations document for the release, this document is emailed to Release Management at the start of the night cycle.
#* Ensure that central does not currently have any known severe regressions or performance issues that would be carried into beta.
# Notify the firefox-ios dev team on #firefox-ios-releases that today is Merge Day
#* Let the team know roughly when you plan on branching
#* Ask them to let you know if there are any urgent pending PRs
# Perform the [https://moz-releng-docs.readthedocs.io/en/latest/how-to/releaseduty/merge-duty/merge_duty.html#release-merge-day-part-ii-a-week-after-merge-day Release Merge Day - part II] steps
# Perform the release management steps in the [https://mozilla.github.io/application-services/book/howtos/releases.html App Services Release checklist]
# Perform the release management steps in the [https://mozilla.github.io/application-services/book/howtos/releases.html App Services Release checklist]
#* Application Services release once and at the start of the beta cycle.
#* Application Services release once and at the start of the beta cycle.
Line 210: Line 215:
# 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]
#* The Firefox iOS release branch is used for beta and rc builds.
#* The Firefox iOS release branch is used for beta and rc builds.
# Send the merge complete email to release-signoff and release-drivers
#** [https://groups.google.com/a/mozilla.org/g/release-signoff/c/qlnvsv4Ky0E Example email]
# Announce the soft freeze is over
# Announce the soft freeze is over
#* Reply back to the soft code freeze announcement email
#* Reply back to the soft code freeze announcement email
Line 441: Line 448:
#* Verify that all approved uplift requests were uplifted to beta
#* Verify that all approved uplift requests were uplifted to beta
# Verify all approved bugs landed on mozilla-release
# Verify all approved bugs landed on mozilla-release
#* Sync with RelEng to merge Beta to Release.
# Perform the [https://moz-releng-docs.readthedocs.io/en/latest/how-to/releaseduty/merge-duty/merge_duty.html#release-merge-day-part-i Release Merge Day - part I] steps
#** Send an email with details of the merge.
# Send the merge complete email to release-drivers
#** Include both [https://groups.google.com/a/mozilla.org/g/release-drivers release-drivers] and [https://groups.google.com/a/mozilla.org/g/release-signoff release sign-off]
# [https://groups.google.com/a/mozilla.org/g/release-signoff/c/xXhHFz8Ko6Q Example email]
#** [https://groups.google.com/a/mozilla.org/g/release-drivers/c/kCYe68Gglng Example email]
# Once the merge is complete, verify that the [https://treeherder.mozilla.org/jobs?repo=mozilla-release Treeherder] tests green/starred
# Once the merge is complete, verify that the [https://treeherder.mozilla.org/jobs?repo=mozilla-release Treeherder] tests green/starred
# Set up Desktop build in [https://shipit.mozilla-releng.net/ Ship-It].
# Set up Desktop build in [https://shipit.mozilla-releng.net/ Ship-It].
Dmeehan
390

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1252053"

Navigation menu