Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checklist for Temurin Release jdk-17 #73

Closed
72 of 73 tasks
smlambert opened this issue Sep 10, 2021 · 15 comments
Closed
72 of 73 tasks

Checklist for Temurin Release jdk-17 #73

smlambert opened this issue Sep 10, 2021 · 15 comments
Assignees
Labels
temurin-release Issues tracking a Eclipse Temurin project release

Comments

@smlambert
Copy link
Contributor

smlambert commented Sep 10, 2021

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 Week Checklist:

Initial Communication Phase


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).


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

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.


Linux Installers Phase

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 karianna added the temurin-release Issues tracking a Eclipse Temurin project release label Sep 10, 2021
@karianna
Copy link
Contributor

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
Copy link

Good to know :)

@SharpBritannia
Copy link

Is there something we should know about the TCK phase?

@smlambert
Copy link
Contributor Author

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
Copy link

bachp commented Sep 29, 2021

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
Copy link

ffays commented Sep 30, 2021

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.

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

@karianna
Copy link
Contributor

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
Copy link

dinvlad commented Nov 10, 2021

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
Copy link
Contributor Author

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
Copy link

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
Copy link
Contributor Author

smlambert commented Dec 16, 2021

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
Copy link

dinvlad commented Dec 16, 2021

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
Copy link
Contributor

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

@sideeffffect
Copy link

For example eclipse-temurin:17.0.1_12-jre

@smlambert
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
temurin-release Issues tracking a Eclipse Temurin project release
Projects
None yet
Development

No branches or pull requests

9 participants