[Release]: 3.2.0-M2

[KyleAure]

Proposal

Should we release a M2 version with the relocation changes made in #555?

Outstanding work

• dependencies: update parent project #832
• dependencies: update parent project in Relocation #833
• https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7153
  • Opened ticket with Eclipse to allow us to push artifacts to the new group id jakarta.concurrent
• Choose group id between jakarta.concurrent vs jakarta.concurrency in Remove enterprise form Package and Group ID #805
• Take up EE12 milestone dependencies #834

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
• Create pull request to https://github.com/jakartaee/specifications
  • upload generated specification documentation
• Update versions in non-build files, such as:
  Documentation:
  • tck/README.adoc
  • concurrency-tck-reference-guide.adoc

[arjantijms]

Should we release a M2 version with the relocation changes made in #555?

Absolutely! +1

[KyleAure]

@arjantijms - I have staged an M2 release. Details below:

Staged release artifacts: https://repo3.eclipse.org/#browse/browse:cu-maven2-staging
Draft release: https://github.com/jakartaee/concurrency/releases/edit/untagged-8df85a088f041562e9cb

Let me know if there is anything I missed or if you could test out pulling and using the artifact from the staged repository and see if it works :D

[arjantijms]

@KyleAure

Thanks! I was just too late with local testing, but I encountered a few things (not necessarily related to the staging):

1. The pom is still depending on the EE 11 version of CDI, not on the 5.0.0-M1 milestone. Since transitive dependencies are highly protected in OSGi based on their major version, I can't use the artefact as-is in GF (a workaround would be to patch it)
2. I tried to guess the coordinates, but this failed. My guess was jakarta.concurrency:jakarta.concurrency-api. It didn't work, obviously. I then remember we used jakarta.concurrent (just removing the enterprise infix). WDYT? Shall we make it jakarta.concurrency to align with the spec name? Or keep jakarta.concurrent to align with the package name?

[KyleAure]

@arjantijms
I opened up the group id discussion to a vote here: #805 (comment) (where the discussion was started)