[Release]: 3.0.4 service release

[KyleAure]

Proposal

If we were to create a 3.0.4 service release I wanted an issue open to track changes we would want to put in

Outstanding work

• TCK Managed Thread Factory APITests, possible for task to complete before interrupt is issued
  • Fixed in 3.1 with commit:

    concurrency/tck/src/main/java/ee/jakarta/tck/concurrent/spec/ManagedThreadFactory/apitests/APITests.java

    Line 66 in 8910404

    CounterRunnableTask task = new CounterRunnableTask(TestConstants.PollInterval);

  • Ensures task waits to be interrupted
• issues/392 TCK challenge for adding support for running Concurrency 3.0 TCK signature tests on Java 21 #393

Check List

Prepare

• Open this issue.
• Complete outstanding work
• (Update TCK Signatures to capture API changes)[https://github.com/jakartaee/concurrency/actions/workflows/release.yml]

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 pre-release 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 pre-release on GitHub to be latest

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.0.4 is Staged

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

Verification Data

file	sha256
concurrency-tck-3.0.4.zip	aa29bfc0bab42d9aa2da518208d9e92cdde80fc17b00dd658954dfd36064a426

@scottmarlow can you test this staged TCK with Wildfly and let me know if there are any other changes you need in this service release. Once I hear back from you I'll go ahead with a publishing this.

[jamezp]

This is passing on WildFly. One important thing to note here is there is a requirement to use jakarta.tck:sigtest-maven-plugin:2.3 here. Older versions will not work because of the change to -IgnoreJDKClass.

OT: I'm working with @scottmarlow to somewhat revert this. IoW revert the -IgnoreJDKClass to work as it did before and add a -IgnoreJDKClasses argument instead. See eclipse-ee4j/jakartaee-tck-tools#39

[KyleAure]

@jamezp I did update the TCK Distribution user guide which says:

concurrency/tck-dist/src/main/asciidoc/concurrency-tck-reference-guide.adoc

Line 99 in 4c30daf

1. **Signature Test Tool** - No action is needed here, but we note that the signature files were built and should be validated with the Maven plugin with group:artifact:version coordinates: **{SigPluginGAV}**, as used by the sample sigtest runner included in the TCK zip. This is a more specific direction than in earlier releases, in which it was left more open for the user to use a compatible tool. Since there are small differences in the various signature test tools, we standardize on this version.

concurrency/tck-dist/src/main/asciidoc/concurrency-tck-reference-guide.adoc

Line 435 in 4c30daf

As mentioned in the prerequisite section the signature file formats across the various signature test tools have diverged and this test suite uses the Maven plugin with group:artifact:version coordinates: **{SigPluginGAV}**.

So it should be clear that users need to use specifically the 2.3 version of the plugin.
If you think anymore documentation should be added let me know. Otherwise, I'll go forward with releasing this.

[jamezp]

@KyleAure No, I think that is sufficient. We were using a very old version anyway :) I say go forward with the release.

[KyleAure]

3.0.4 is Released

• GitHub Tag: 3.0.4
• GitHub Branch: RELEASE-3.0.4
• GitHub Release: 3.0.4
• Maven Central: jakarta.enterprise.concurrent-api
• Promoted TCK Dist: concurrency-tck-3.0.4.zip

Verification Data

file	sha256
concurrency-tck-3.0.4.zip	aa29bfc0bab42d9aa2da518208d9e92cdde80fc17b00dd658954dfd36064a426