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

GA

• Replace aggregated jobs for the prior release with the single job component options (with 3 retries – example)

• Take a snapshot of prior release GA data: make sippy && ./sippy snapshot --name "4.16 GA" --release "4.16" --database-dsn="$DSN_PROD"

export VERSION_THAT_WENT_GA=4.16
export DSN_PROD=$(oc get secret postgres-aws -o json|jq -r .data.dsn|base64 -D)

git clone https://github.com/openshift/sippy.git ; cd sippy
make sippy
./sippy snapshot --name "${VERSION_THAT_WENT_GA} GA" --release "${VERSION_THAT_WENT_GA}" --database-dsn="${DSN_PROD}" 

• Update BigQuery Releases table for the GADate, example: UPDATE `openshift-ci-data-analysis.ci_data.Releases` SET GADate = “2023-12-05” WHERE Release="4.15"
• Update Disruption Dashboard default Releases variable to the new development release. Open dashboard in a fresh tab, select the new Release under development to focus on, hit the Save icon (floppy disk), and check “Save current variables as dashboard default”.