[Release]: 3.1.0 GA

[KyleAure]

Proposal

Let's start a plan for the 3.1.0 GA release! 🎉

Outstanding work

• Fix AnnotationFullTests, Make WAR File a Bean Archive #473
• Update certifcation documentation #485
• Help automate specification project release review #477
• Clarify test counts in TCK documentation #484
• Update license for Jakarta EE 11 #483

Challenges

• Adjust tests that use qualifiers with an *Definition annotation that is put on a class not scanned by CDI #489
• DeploymentDescriptorFull/WebTests Adds Resource Definitions with Qualifiers on a CDI Bean #494

Check List

Prepare

• Open this issue.
• Complete outstanding work
• Update TCK Signatures to capture API changes

Stage release

• Build and stage artifacts to staging repository
• Build and stage the TCK distribution artifact to download.eclipse.org
• Update this issue with a comment that links to the staged artifacts and the generated GitHub branch and tag
• Create a draft on GitHub

Verify and modify

• Ask for feedback from the community to verify the staged artifact has all the expected changes.
• If anything needs to be added before publishing do that now and repeat the Stage Release section

Publish release

• Publish staged artifacts to the public repository
• Publish staged TCK distribution artifact to download.eclipse.org
• Update this issue with a comment that links to the published artifacts and the generated GitHub branch and tag
• Modify the draft release on GitHub to be latest or pre-release

Follow up

• Email the Concurrency Mailing list to have a Jakarta Steering Committee member promote the TCK Distribution publically
  • via Jenkins build
• Update versions in non-build files, such as:
  Documentation:
  • tck/README.adoc
  • concurrency-tck-reference-guide.adoc

[KyleAure]

3.1.0 GA is Staged

• GitHub Tag: 3.1.0
• GitHub Branch: RELEASE-3.1.0
• GitHub Release DRAFT: 3.1.0
• Staging Repo: jakartaenterpriseconcurrent-1018

Notes

I double checked to make sure the two dependency updates between RC2 and GA versions did not affect the checksums for the following artifacts:

• API RC2 MD5: fe3f138c0e1ff6d600266537e3ee9016
• API GA MD5: 7c177355fa619a2ae465c82cac417191
• TCK RC2 MD5: d0ae359cdf7bcfc0f66e9b354067a0fd
• API GA MD5: 7ee16d099de76a1687769e517b911aee

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.

[KyleAure]

3.1.0 GA is Re-staged

• GitHub Tag: 3.1.0
• GitHub Branch: RELEASE-3.1.0
• GitHub Release DRAFT: 3.1.0
• Staging Repo: jakartaenterpriseconcurrent-1019

Verification Data

The checksums are as follows:

• API MD5 : 7c177355fa619a2ae465c82cac417191 [unchanged]
• TCK MD5: b9eabfce9b7abab510ff86df758207e3 [changed]

FYI - @njr-11 @aubi

[KyleAure]

Created specification project release review: jakartaee/specifications#733

[KyleAure]

3.1.0 GA is Re-staged

• GitHub Tag: 3.1.0
• GitHub Branch: RELEASE-3.1.0
• GitHub Release DRAFT: 3.1.0
• Staging Repo: jakartaenterpriseconcurrent-1020
• Staged TCK Dist: concurrency-tck-3.1.0.zip

Verification Data

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

[KyleAure]

3.1.0 GA is Re-staged

• GitHub Tag: 3.1.0
• GitHub Branch: RELEASE-3.1.0
• GitHub Release DRAFT: 3.1.0
• Staging Repo: jakartaenterpriseconcurrent-1021
• Staged TCK Dist: concurrency-tck-3.1.0.zip

Verification Data

file	sha256
concurrency-tck-3.1.0.zip	9539826afc510300f6873477a8ba6ae0860883ecd659d629fb62f4e77b457c23

FYI - @OndroMih @arjantijms @njr-11

[KyleAure]

3.1.0 GA is Re-staged

• GitHub Tag: 3.1.0
• GitHub Branch: RELEASE-3.1.0
• GitHub Release DRAFT: 3.1.0
• Staging Repo: jakartaenterpriseconcurrent-1022
• Staged TCK Dist: concurrency-tck-3.1.0.zip

Verification Data

file	sha256
concurrency-tck-3.1.0.zip	a519066b945b6a10ca1a634c9158c038c2e6f52db6c96e988e977740e1fedc56

FYI - @aubi @arjantijms @njr-11