Closed KyleAure closed 1 month ago
I double checked to make sure the two dependency updates between RC2 and GA versions did not affect the checksums for the following artifacts:
FYI @mswatosh @njr-11 - I checked the diffs between the JARs and I think no matter what we do the GA version will have a different checksum then RC2 because of the change in
META-INF/maven/jakarta.enterprise.concurrent/jakarta.enterprise.concurrent-[api|tck]/pom.properties
META-INF/maven/jakarta.enterprise.concurrent/jakarta.enterprise.concurrent-[api|tck]/pom.xml
The switch from 3.1.0-RC2
to 3.1.0
are reflected in these files meaning the checksums will not match.
I think we need to inquire about the checksum requirement for compatible implementations. If RC2 and GA only have diffs in META-INF I would think certifying against either checksum should be valid.
The checksums are as follows:
FYI - @njr-11 @aubi
Created specification project release review: https://github.com/jakartaee/specifications/pull/733
file | sha256 |
---|---|
concurrency-tck-3.1.0.zip | ad1d52fdf9648db8d2afbaefd480d8995be47b59c605b439d69ededf4da4fcd5 |
jakarta.enterprise.concurrent-tck-dist-3.1.0-dist.zip | 44be17650689c27ba76c8849655c69621980b97893e2bb6b1def39c386a57347 |
Seems to me the TCK User Guide PDF has date metadata that cannot be removed resulting in different SHAs for these two artifacts since they are generated at different times. The only resolution to this would be to take the TCK Distibrution zip from the staging repository and dumping that into download.eclipse.org but that would require in an entire re-write of that Jenkins job. Not sure if that is worthwhile doing at this late stage. ^^ FYI @njr-11 @edbratt
file | sha256 |
---|---|
concurrency-tck-3.1.0.zip | 9539826afc510300f6873477a8ba6ae0860883ecd659d629fb62f4e77b457c23 |
FYI - @OndroMih @arjantijms @njr-11
file | sha256 |
---|---|
concurrency-tck-3.1.0.zip | a519066b945b6a10ca1a634c9158c038c2e6f52db6c96e988e977740e1fedc56 |
FYI - @aubi @arjantijms @njr-11
file | sha256 |
---|---|
concurrency-tck-3.1.0.zip | a519066b945b6a10ca1a634c9158c038c2e6f52db6c96e988e977740e1fedc56 |
Proposal
Let's start a plan for the 3.1.0 GA release! 🎉
Outstanding work
Challenges
Check List
Prepare
Stage release
draft
on GitHubVerify and modify
Stage Release
sectionPublish release
draft
release on GitHub to belatest
orpre-release
Follow up