Review the release checklist in https://docs.google.com/document/d/1yhshBaryFjGTAnEZO-bFAmqauzo-EaYf2Ez2qKeZtKo/edit#heading=h.wc217iui75a1

Feature freeze / main branch opens for next release

Prior to branch cut

• Verify aggregated jobs are enabled for the next release (example)
  • Files are created by DPTP, we need to verify correct upgrade from streams are set and `multiJobAnalysis`flag is set for multi job analysis configurations
• As payloads become available for each arch and stream, forcefully accept the first two of each. This is required for micro upgrade jobs to run, as well as for multi arch payloads to be constructed. Check all release-controller links of the form: https://xxxx.ocp.releases.ci.openshift.org where xxxx = amd64, multi, s390x, arm64, ppc64le
• Verify that the next release has nightly builds flowing to so that we gather historical data for aggregated jobs in time for main branch opening. If nightlies are not being built, reach out to ART.  If CI has failures reach out to Test Platform. There were a few extra steps needed historically. Check the above document for details.
• Monitor informing jobs - new informing jobs for telco, cnv, etc. may need additional config changes (like ROSA) we should monitor payloads for broken job and notify teams as needed.

After branch cut (Until TRT-1774 is completed)

• Update the BigQuery Releases table for new dev release
• Add a CR view for the new release?
  • Update the CR dashboard to include the new view
• Add next release to DPCR deployment configuration (example)
  • It is likely ok to do this prior to the release being added and branch cut but once we clear the need to wait to add the release from sippy we should maintain the order of adding the release first then updating DPCR