-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
October 2023 Release Status per Platform, Version & Binary Type #6
Comments
The column headers under "JDK21.0.XX+Y ????" say "jdk20" instead of "jdk21". |
Thanks, fixed. |
JDK 21.0.1 is now also officially released https://www.oracle.com/java/technologies/javase/21-0-1-relnotes.html |
When can we expect JDK 17.0.9 for windows x64? |
@rec-bln it's blocked by adoptium/aqa-tests#4831, which we are working on right now. |
Is there a plan to release JDK 21 ppc64 build? |
See adoptium/adoptium-support#917 (TL;DR: maybe) |
thanks! Looking forward to get the release :) thanks for your work on this! |
Do you mean aix/ppc64 or Linux/ppc64le? The former is a definite no for now as some of the new features are not yet implemented on AIX. Linux/ppc64le has been shipped now. |
@sxa |
Hi folks - The Windows x64 builds seem to be separated into a separate release at https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.9%2B9.1 , I guess due to adoptium/aqa-tests#4831 - are these going to be merged into the same GitHub release as everything else or is this the permanent situation for this release? |
It will be permanent to avoid any confusion for people who picked up the old one and may have a record of the SHAs etc. If you pull from the API you should receive the latest version that is available. |
@sxa the x64 binaries were never published to the old release though. This is a bit unfortunate. We didn't use the APIs - IIRC due to rate limiting (not sure if relevant now), and 1 less dependency on external infra. Guess will need to migrate. |
During update, there is a problem with package version under ubuntu 2004,
Also output from apt-get during packer installation:
|
@sxa Unfortunately the API doesn't really work cleanly either, as to get a deterministic version (compulsory in order to do reproducible builds when repackaging Temurin), it still requires the caller to be aware of the 404s: https://api.adoptium.net/v3/binary/version/jdk-17.0.9%2B9/windows/x64/jre/hotspot/normal/eclipse?project=jdk |
@chadlwilson You can use "latest", try: |
@andrew-m-leonard Thanks, but |
@huczas updated. temurin-11-jdk_11.0.21.0.0+9_amd64.deb should be there now. Could you try it again? Thanks! |
Thanks for the feedback @chadlwilson we will bear that scenario in mind for next time. |
Yep I do understand the concern and it has to be balanced with the ability for us to respin with platform-specific fixes without changing the artefacts which have already been uploaded which has caused us some problems in the past. The way we've implemented the rebuilds by giving it a new identifier is generally the safest option.
Unfortunately yes that is correct if you require full reproducibility of a specific build. |
Thank you for fast fix, it's working now :-) |
All done, close this one. |
Sharing information in this issue since the TCK work is being tracked in temurin-compliance private repo not visible to the community (as per the OCTLA). Risks and expectations for timing on the release are listed in this issue comment. Primary platforms (x64 Linux/Windows/OSX and aarch64 Linux/OSX) in bold are prioritized, secondary platforms not in bold follow in no particular order (as machine resources are available). We retrospectively measure and track how well we do against these targets in these Adoptium Release Scorecards in order to continuously assess and improve.
✔️ results in these Tables means the activity has successfully completed.
⏳ results means that we are actively working on closing off the runs needed for this version, platform, binaryType.
⛔ means there is no build planned for that version/platform combination.
⏸️ means activity not yet started.
JDK8u392-b08
jdk-11.0.21+9
jdk-17.0.9+9
JDK21.0.1+12
The text was updated successfully, but these errors were encountered: