M1 of Concurrency 3.1 spec is required by November 28

[njr-11]

Ed Burns sent out an email on 2023/10/02 to the Jakarta specification leads list, titled
[jakartaee-spec-project-leads] ACTION: EE 11 Milestone 1: component spec M1 release by 2023-11-28

I was on the list for a different spec, but it applies to all Jakarta EE 11 specs including this one as well, so I'm opening this issue for it to ensure it is covered in Concurrency spec as well because there have been API additions made in this spec for EE 11.

Given the difficulty of getting these releases created last release, it would make sense to start on this well in advance of the deadline.

Copied from the email:

This message is your notice that the EE 11 platform project expects you, as a component spec project, to produce your first milestone release for EE11 by 23:59 EST on 2023-11-28.

Requirements

We want to keep the bar low for EE 11 M1. We realize we are all trying to get our milestone release producing engines started. M1 does not require a TCK or an implementation, though it would be better if you had those. We will require those for M2. Here's what you need to hit M1.
API jar released to maven central
groupId: same as EE 10
artifactId: Same as EE 10
version: whatever your version number is for EE11 followed by "M1" For example for Jakarta Faces it would be 5.0.0-M1.
Spec document
Javadocs
XML schemas (if the spec has XML schemas)

Prepare

• Open this issue.
• Complete outstanding work

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

[mswatosh]

Based on the Project board for 3.1, this is what will be included in the M1

• @Schedule Annotation #98
• TCK jar test code source and consistent totals of results #217
• TCK enhancement poll for task completion instead of sleeping #223
• Support Java 9 Flow and ReactiveStream #257
• ManagedExecutorService and ContextService default resources as injectable CDI beans #229
  I think this is more than sufficient for the M1, and I don't see anything else being worked, so I think we're at a good point to do the M1 release

[KyleAure]

Milestone 1 is staged:

• GitHub Tag: https://github.com/jakartaee/concurrency/tree/3.1.0-M1
• GitHub Branch: https://github.com/jakartaee/concurrency/tree/RELEASE-3.1.0-M1
• GitHub Prerelease: https://github.com/jakartaee/concurrency/releases/tag/3.1.0-M1
• Staging repo: https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/

Please review the Milestone 1 staged release and comment on this issue if there are any additions/deletions needed before we go forward with publishing the Milestone 1 release

[KyleAure]

Milestone 1 is released:

• GitHub Tag: https://github.com/jakartaee/concurrency/tree/3.1.0-M1
• GitHub Branch: https://github.com/jakartaee/concurrency/tree/RELEASE-3.1.0-M1
• GitHub Release: https://github.com/jakartaee/concurrency/releases/tag/3.1.0-M1
• Public Repo: https://jakarta.oss.sonatype.org/content/repositories/public/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/
• Maven Central: https://repo1.maven.org/maven2/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/