390
edits
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:55, 18 October 2024
, 18 October 2024Replaced the end of early beta commit instructions with the automated steps
(Added a step covering the mozilla-beta->mozilla-release no-op trial run) |
(Replaced the end of early beta commit instructions with the automated steps) |
||
| Line 474: | Line 474: | ||
==The following needs to be performed at the End of Early Beta== | ==The following needs to be performed at the End of Early Beta== | ||
Please Note: This is performed on the Friday at the midday point of the beta cycle, see the Releases Scheduling google calendar. This is typically after beta 6 has been released. This should be done in | Please Note: This is performed on the Friday at the midday point of the beta cycle, see the Releases Scheduling google calendar. This is typically after beta 6 has been released. This should be done in before pushing any other uplifts to beta after beta 6. | ||
# | # Go to [https://treeherder.mozilla.org/ Treeherder]. | ||
# | # Select the beta repo. | ||
# | # On the latest push, click on the down arrow at the top right corner. | ||
# | # Select “Custom push action…” | ||
#* | # Choose ''merge-automation'' from the dropdown. | ||
# | # Insert the following payload and click trigger. | ||
#* "force-dry-run: true | |||
behavior: early-to-late-beta | |||
push: true" | |||
# After the job runs, verify that the commit was pushed to the mozilla-beta repo, see [https://hg.mozilla.org/releases/mozilla-beta/rev/29e6215562511ffef7bfa73bed97093ec3d8cdd4 example]. | |||
==The following needs to be performed at the end of the Beta Cycle== | ==The following needs to be performed at the end of the Beta Cycle== | ||