Discussion: Review release code freeze/tagging/branching policy

[adamfarley]

Summary

To decide the disposition of Adoptium repositories during a release (specifically freezing, tagging, and branching).

Details

This includes:

• Whether a code freeze is needed at all.
• Which repositories should be tagged or branched during a release.
• (Optional) Whether said branches should be automatically frozen by default.

Original retrospective comment.

Discussion notes so far

• Which repositories need to be tagged/branched for a release?
• Is code freeze really necessary? It adds several additional steps in the release checklist. Should we just be tagging and using all of the relevant Temurin repos from SHAs/tags (or if necessary branches)?

[adamfarley]

Current freezing policy: https://github.com/adoptium/temurin-build/blob/master/RELEASING.md#enable-code-freeze-on-the-build-repositories

master branch:

• github-release-scripts https://github.com/adoptium/github-release-scripts
• containers https://github.com/adoptium/containers
• installer https://github.com/adoptium/installer
• mirror-script https://github.com/adoptium/mirror-scripts

release branch:

• temurin-build https://github.com/adoptium/temurin-build
• ci-jenkins-pipelines https://github.com/adoptium/ci-jenkins-pipelines
• jenkins-helper https://github.com/adoptium/jenkins-helper