Checklist for Temurin Release 19+36

[gdams]

This Temurin release checklist based on the release doc captures what activities must happen during a release.

The target release date is: September 20, 2022

The release champion for this release is: George Adams @gdams

Planned absences during the release cycle: Red Hat 20th-23rd

The role of the release champion is to ensure that all release activities listed in this checklist get completed (by delegation to the broader team or by the release champion themselves). The final task of the release champion during a release is to confirm that all items in the checklist were completed satisfactorily and the release can be declared complete.

Everyone participating in a release, including the release champion are requested to provide feedback into the release retrospective so that the release process can be continuously improved (through simplification and/or automation).

---

One Week Prior to Release:

• [x] Release Champion named whose responsibility is to ensure every item in this checklist gets completed
• [x] Declare code freeze to ensure stability of build systems and infrastructure during release process
• [x] Disable nightly testing to free up resources and ensure no competing jobs during release week
• [x] Update aqaReference to update with new git tag for 'aqaReference' to be used in release pipeline

---

Release Week Checklist:

• [x] Add website banner (automate* via github workflow in website repository) - Announce that we target releases to be available within 48-72 hours of the GA tags being available

• [x] Check Tags have been released upstream - Look for mailing list announcements and -ga tags in version control.

• [x] Check Tags have been Mirrored Mirrors.

• [x] Launch build pipelines for each version being released (as per release doc) once release tags are available via launch page in Jenkins. Provide links in this issue to each version's pipeline build(s). There may be multiple pipelines per version if primary and secondary platforms are separated to expedite the release. In some cases, where there are unforeseen configuration or infrastructure issues, reruns may be needed.

  • jdk19 pipeline(s):
  • primary jdk19 pipeline: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk19-pipeline/216/
    • rerun(s):
  • secondary jdk19 pipeline: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk19-pipeline/217/
    • rerun(s):

• [x] Add links to the status doc to indicate per-platform builds ready

• [x] Summarize test results. Find each launched build pipeline in TRSS to view a summary of test results. Can use the Release Summary Report feature in TRSS to generate a summary of failures, history and possible issues in markup format to be added to this issue as a comment.

• [x] Triage each build and test failure in the release summary report (following the Triage guidelines) and determine blocking or non-blocking. Supply links to triage issues or docs for each version here.

  • jdk19 triage summary: https://github.com/adoptium/aqa-tests/issues/3976

• [x] Fix blocking failures if they exist and confirm others are non-blocking.

• [x] Confirm Temurin-compliance items completed, per platform/version/binaryType

• [x] Get PMC 'ready to publish' approval, once no blocking failures exist.

• [x] Publish the release (run the restricted access release tool job on Jenkins)

• [x] Verify binaries published successfully to github releases repo and website (automate*, this could also be an automated test)

• [x] Publish updates to the containers to dockerhub

• [x] **Edit the Homebrew Temurin Cask and replace the version and sha256 as appropriate. This means for Homebrew users that they install the latest by default and can use the @ notation to install older versions if they wish.

• [x] Update support page (automate* github workflow to create a PR to update support.handlebars)

• [x] Update release notes (automate* - github workflow to create update for release notes page)

• [x] Trigger linux installers pipeline currently it is part of the build pipelines (will eventually be updated to run independently)

• [x] Publicize the release via Slack #release channel and Twitter (can be partially automated)

• [x] Declare code freeze end opening up the code for further development

• [x] Remove website banner (automate* via github workflow in website repository)

• [x] Declare the release complete and close this issue

[gdams]

Leaving this open until we've shipped Windows x86

[smlambert]

Closing as complete

[jpdev01]

Can we insert Java 19 into the supported versions?

https://github.com/actions/setup-java#supported-version-syntax

[danthe1st]

@jpdev01 As far as I know, this is not managed by Adoptium/the Eclipse Foundation. It might be best to create an issue or PR in https://github.com/actions/setup-java

[jpdev01]

@danthe1st I made a mistake in the pull request while commenting, sorry guys.