Checklist for Temurin Release jdk-17

[smlambert]

This Temurin release checklist based on the release doc captures what activities must happen during a release. Sept 2021 Zenhub Release report (use browser extension for best viewing).

The target release dates are:

• Tag expected on Sept 14
• TCK test material expected days later (Sept 17?)
• Target date to close all related activities in this checklist is Sept 30th

The release champion for this release is: Martijn Verburg
Temurin-compliance status from: Andrew Leonard, Shelley Lambert
AQAvit triage support from: Sophia Guo, Shelley Lambert
Unavailable for release week: Stewart Addison, Simon Rushton

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, is 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:

• Release Champion named whose responsibility is to ensure every item in this checklist gets completed
• Declare code freeze to ensure the stability of build systems and infrastructure during the release process
• disable nightlies for Java 17 release ci-jenkins-pipelines#187 to free up resources and ensure no competing jobs during release week.
• Check jobs running on ci.adoptopenjdk.net to make sure there are no other hanging jobs.
• [ ] Update list of CA certificates if required, following this security/README - This was not required as certs have not updated since July
• Run a trial release pipeline to ensure fewer surprises on release day (typically against a milestone build)
  • Primary Platforms - Results Triage
  • Secondary Platforms - Results Triage

---

Release Week Checklist:

Initial Communication Phase

• mark jck compliant builds as we did on old website adoptium.net#167 - announce availability starting from the 20th of Sept
• Inform the Slack Community of the start of the release and reference the release channel for updates.

---

Binary Production Phase

Please update #74 as you confirm each build is completed (yes we're duplicating checkboxes here, but we'll deduplicate the process for next time).

• Produce JDK 17 Binaries for Primary Platforms temurin-build#2708
  • primary jdk17 pipeline: pipeline run
    • Linux x86-64
    • Mac OS X x86-64
    • Windows x86-64 - False alarm on respin
  • optional rerun(s):
• Produce JDK 17 Binaries for Secondary Platforms temurin-build#2709
  • secondary jdk17 pipeline: pipeline run
    • aarch64 Linux
    • ppcle64 Linux
    • s390x Linux
    • [x] ppc64 AIX Needed respin due to connection lost to host
    • x32 Windows
    • arm32 Linux
    • [x] x64 alpine-Linux (Needed to be respun)
    • aarch64 Mac
  • optional rerun(s):
    • x64 alpine-Linux
    • ppc64 AIX

---

AQAVit Triage Phase

Please update #74 as you confirm each build is tested (yes we're duplicating checkboxes here, but we'll deduplicate the process for next time).

• Triage JDK 17 Primary Platform Pipeline aqa-tests#2853
  • primary jdk17 pipeline:
    • Linux x86-64 - Triage by Sophia, Andrew
    • Mac OS X x86-64 - all pass
    • Windows x84-64 - Triage by Shelley
  • optional rerun(s):
• Triage JDK 17 Secondary Platform Pipeline aqa-tests#2854
  • secondary jdk17 pipeline:
    • aarch64 Linux - Triage by Sophia
    • ppcle64 Linux - all pass
    • s390x Linux - Triage by Sophia
    • ppc64 AIX - Initial Triage by Martijn - will need further triage by AIX experts
    • x32 Windows - Triage by Andrew
    • arm32 Linux - Triage by Sophia
    • x64 alpine-Linux - Triage by Sophia
    • aarch64 Mac - Triage by Martijn
  • optional rerun(s):

---

Compliance Confirmation Phase

• Sept 2021 Release Status per Platform, Version & Binary Type #74 Confirm TCK status is passing 👍 from Temurin-compliance project
  • primary jdk17 pipeline:
    • Linux x86-64
    • Mac OS X x86-64
    • Windows x84-64
  • secondary jdk17 pipeline:
    • aarch64 Linux
    • ppcle64 Linux
    • s390x Linux
    • ppc64 AIX
    • x32 Windows
    • arm32 Linux
    • x64 alpine-Linux
    • aarch64 Mac

---

Publish Binaries and Windows/Mac Installers Phase

For each platform do the following (you can often do this in groups of platforms):

• Get PMC 'ready to publish' approval, once no blocking failures exist.
• Publish the release (run the restricted access release tool job on Jenkins)
• Verify binaries published successfully to GitHub releases repo
• Check API (automate*, this could also be an automated test)
• Check Website (automate*, this could also be an automated test)
• Update Sept 2021 Release Status per Platform, Version & Binary Type #74
• Platforms:
  • primary jdk17 pipeline:
    • Linux x86-64
    • Mac OS X x86-64
    • Windows x84-64
  • secondary jdk17 pipeline:
    • aarch64 Linux
    • ppcle64 Linux
    • s390x Linux
    • ppc64 AIX
    • x32 Windows
    • arm32 Linux
    • x64 alpine-Linux
    • aarch64 Mac

---

Containers Phase

• Containers Epic

Follow the instructions in the Containers README to execute the release of the containers.

Platforms:

• Platforms:
  • primary jdk17 pipeline:
    • Linux x86-64
    • Windows x84-64
  • secondary jdk17 pipeline:
    • aarch64 Linux
    • ppcle64 Linux
    • s390x Linux
    • arm32 Linux
    • x64 alpine-Linux

---

Homebrew phase

Edit the Homebrew Temruin 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.

• 17

---

Linux Installers Phase

• Installers Epic

Instructions below are out of date and will be updated when we get to this stage

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

---

Communications Phase

• Update support page (automate* github workflow to create a PR to update support.handlebars)
• Update release notes (automate* - github workflow to create update for release notes page)
• Publicize the release via Slack #release channel, Blog Post, and Twitter (can be partially automated)
• Declare code freeze end opening up the code for further development
• Remove website banner (automate* via github workflow in website repository)
• Declare the release complete and close this issue

[karianna]

One thing to note for users is that the vendor has been changed from Eclipse Foundation to Eclipse Adoptium after long debates at the Working Group :-).

[CyberFlameGO]

Good to know :)

[AlLiberali]

Is there something we should know about the TCK phase?

[smlambert]

re: #73 (comment) - short answer is that its slow work to run the compliance suite of tests at the project

Here are some stats for July release, you can extrapolate from those what September release looks like in Temurin-compliance project where the TCKs are run. (more people and machines would be helpful). Also noting, we also do not have early access to TCK test material, so we received them on Thursday/Sept16 afternoon and that is the very first chance we have had to run them against the Temurin binaries.

[bachp]

I don't know if this is the right place to report this. But is it expected that the arm (32-bit) release contains a lib/client and lib/server directory. While all other platforms only contain a lib/server.

I noticed it because both directories contain a libjvm.so and this confused bitbake.

[ffays]

Why the JRE assets are not part of the JDK 17+35 official release whereas they were included a couple hours ago by the nightly build (i.e. JDK 17 2021-09-22 02:48 beta) ?

cf.

• jdk-17+35
• jdk17-2021-09-22-02-48-beta

Could you please include the JRE assets in the next official release ?

[karianna]

We are not releasing JREs (the ones being produced by the nightlies were for us to see what the (now-defunct) legacyJRE build target produces so we can build better docs / tooling for the post JRE world.

[dinvlad]

Could you elaborate why JREs are not released for 17? Is there a plan for the migration? We tried jlink builds, but they're breaking our services unlike the official JRE images..

[smlambert]

re: #73 (comment) the PMC will be revisiting this decision in next week's meeting based on all of the community feedback surrounding it.

[racevedoo]

re: #73 (comment) the PMC will be revisiting this decision in next week's meeting based on all of the community feedback surrounding it.

any news regarding the jre decision? @smlambert

[smlambert]

re: #73 (comment) We have published them yesterday, https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.1%2B12... blog post will be drafted to more broadly announce, but you should be able to pick them up via API / website shortly (if not already).

[dinvlad]

Thanks! Would it be possible to also publish this to the Docker Hub (along with already existing tags for 11-jre? Without those, not sure how many folks would actually benefit from it.. And for example, we consume Temurin just by building on top of its "blessed" base images, so pulling from another source is not an option in that case, unfortunately.

[karianna]

@gdams have the JRE based docker images been uploaded to DockerHub?

[sideeffffect]

For example eclipse-temurin:17.0.1_12-jre

[smlambert]

Am closing this issue as we are tracking AIX jdk17 release blocker elsewhere (in a Temurin-compliance repo).