Closed sxa closed 2 years ago
@smlambert Can you prep a suitable aqaReference for this please?
@sophia-guo has prepped 0.9.4.2-release branch of aqa-tests which can be used as the aqaReference for this EA build. (thanks Sophia!).
Pipelines in progress:
Aqa-tests triage issue https://github.com/adoptium/aqa-tests/issues/3947
I've run the release tool with a TAG
of jdk8u352-b05-ea
and with the RELEASE
checkbox enabled (otherwise it requires a timestamp...) I pre-created the release in github marked as a Pre-release
to prevent the release tool marking it as the latest GA.
The builds can be retrieved via the API using something like this Linux/x64 example: https://api.adoptium.net/v3/binary/version/jdk8u352-b05-ea/linux/x64/jdk/hotspot/normal/eclipse
arm32 still awaiting a fix for https://github.com/adoptium/mirror-scripts/issues/33
Linux/arm32 pipeline in progress: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/2269/
In addition to the platorms released in the earlier comment from the initial set in https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/2258/ I have now published Solaris and AIX from https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/2259/
arm32 was also published last night from https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/2269/ so all platforms have now been shipped.
In terms of marketing @smlambert will be finalising a blog post with easier to digest links to the ea releases, and in the meantime Andrew Haley has tweeted about it which I have retweeted at https://twitter.com/sxaTech/status/1567562561473626114 so this side of it can now be considered complete.
Temurin should build and test a version of JDK8 based on
jdk8u352-b05
which includes a fix for an undefined behaviour bug injava.lang.ref.reference
(See https://access.redhat.com/articles/6964484). This is a change which can potentially break customers' applications and would benefit from more wide scrutiny and testing before the next version is formally releases. This will be "Maintenance Update 4" for JDK8 as per https://jcp.org/en/jsr/detail?id=337This should be a beta / early-access deliverable built with options such as
--with-milestone=beta --with-user-release-suffix=ea --with-build-number=b05
and a suitableaqaReference
The openjdk8-pipeline should be initiated as a nightly build (to avoid it having
--with-milestone=fcs
and therefore not shown as abeta
) with anscmReference
ofjdk8u352-b05_adopt
andoverridePublishName
set tojdk8u352-b05_ea
This should allow us to release with a github name of
jdk8u352-b05_ea
and the build will contain the following output fromjava -version
: