[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: https://github.com/jakartaee/concurrency/blob/891040463fe1fade237948d1fe5cfd42ecc5b5a7/tck/src/main/java/ee/jakarta/tck/concurrent/spec/ManagedThreadFactory/apitests/APITests.java#L66
  • Ensures task waits to be interrupted
• [ ] https://github.com/jakartaee/concurrency/pull/393

Check List

Prepare

• [X] 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