Concurrency 3.1 plan

[njr-11]

Plan Review PR Template
When creating a specification project plan review, create PRs with the content defined as follows.

Include the following in the PR:

• A directory in the form wombat/x.y where x.y is the release major.minor version.
• An index page wombat/x.y/_index.md following template
• Spec. Page Title should be on the form "Jakarta Wombat X.Y (under development)"
• Includes a plan for the release. Usually, a couple of statements is enough. Otherwise, a link to a document describing the release.
• Includes a detailed description of any backward incompatibility (Mark with N/A and check if none)
• Declares optional features if there are any (Mark with N/A and check if none)
• Includes minimum Java SE version
• Describe any updates or required changes including splitting out the TCK (Mark with N/A and check if not planned)
• Link to updated release record

[netlify]

✅ Deploy Preview for jakartaee-specifications ready!

Name	Link
🔨 Latest commit	8293ad2
🔍 Latest deploy log	https://app.netlify.com/sites/jakartaee-specifications/deploys/64bc3a94f334da000776d685
😎 Deploy Preview	https://deploy-preview-617--jakartaee-specifications.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[edbratt]

I hope it's okay, I replaced the initial commit description with the Plan Review template (we can check off many more tasks that way).

[edbratt]

1. Spec PR for Plan / Proposal

• PR uses template
• Directory of form {spec}/x.y
• (Optional) PDF of form jakarta-{spec}-spec-x.y.pdf ("-spec" preferred but not required) -- NA
• (Optional) HTML of form jakarta-{spec}-spec-x.y.html ("-spec" preferred but not required) -- NA
• Index page {spec}/x.y/_index.md following template
• Index page {spec}/_index.md following template
• No other files (e.g., no jakarta_ee_logo_schooner_color_stacked_default.png)

2. _index.md

• Link to project PMI plan of the form https://projects.eclipse.org/projects/ee4j.{spec}/releases/x.y/plan
• Scope statement changes -- This might be any of
  • Revised specification document, possibly with markup indicating changes
  • Short description of proposed changes
  • List of issues
    • If many issues are involved consider using an epic (issue of issues) and only provide high-level summary.
  • If the version update includes material that is outside the original scope, (i.e. if a feature were to be refactored to another specification or if some major additional functionality is proposed), this should be highlighted.
• High-level Plan -- If intended to align with a more broad release (i.e. Jakarta EE major release) reference that plan (or plan body). Indicate the milestones intended for this specification update (any planned checkpoints: feature complete, code complete, TCK complete, target ballot date).
• How to communicate with the Specification committer team (team list, issue tracker, etc.)
• Any additional requirements or details that would be necessary to complete this specification (dependencies, resource requirements, etc.) -- None are noted

3. Proposed Spec PDF (Optional) -- Not included with initial Plan

• Correct spec title, clearly marked preliminary -- NA
• Correct Eclipse copyright line -- NA
• Must indicate DRAFT or SNAPSHOT -- NA
• Correct Logo -- NA

4. Proposed Spec HTML (Optional) -- Not included

• Same as PDF -- NA

5. TCK

• Brief outline describing how TCK will be developed.
• Name or list of target implementation partners

6. EMO Requirements
   TBD
   • An issue will be created by the EMO to track the release review.

[edbratt]

I apologize for the delay reviewing this PR.

I would recommend the following, to facilitate approval:

The list of features/changes, would be improved by including issues IDs. I don't feel qualified to make these changes but it appears this might be a good starting point:

• Integration with Java 21 Virtual Threads, Support Loom Virtual Threads, Interoperability with Structured Concurrency
• Java Flow/ReactiveStreams and context propagation, Support Java 9 Flow and ReactiveStream
• Replace more features from EJB, such as Schedule and Lock annotations, De-empasise EJB, JNDI, Resource-refs, etc. ...
• Become more CDI-centric, Concurrency Dependency Issues
• Specification bug fixes and clarifications, Context Service chapter not updated in Specification
• TCK fixes and enhancements, TCK Improvements for 3.1

According to the mentor checklist, the page is improved by including, how to contact the team. You might consider adding:

Community input is encouraged. Your comments to the issues (or on any Concurrency Issue in our issue tracker) or you may join the Concurrency Developer mailing by clicking the subscribe button on this page.

The mentor checklist asks when Milestone releases will be available -- I presume this means something like a candidate build that other projects or community members could use to assess/work with the proposed changes. Do you have any estimates for that yet?

Once we have agreed if we will make these changes, we can start the "Plan Ballot"

[edbratt]

Please see comments in 'conversation'

[edbratt]

This is an informative comment --
I am to remind the specification committer team of the various process requirements and also the support that is available from the various committees. This can be done via e-mail or a face-to-face meeting as appropriate.

• Pointers to various written resources (such as Specification Process Guide, TCK Process Guide, Eclipse Developement Process, etc.)
• Remind the team that the EFSP requires at least one checkpoint update every twelve months.
• Progress Reviews may be required as requested by the Specification committee.
• Remind the team they are obligated to inform the Specification Committee if their work requires evolution to the plan (major features in or out) and/or any significant changes to checkpoint targets.
• Remind team of the IP review process for all new, and changes to existing, third party requirements
• Remind the team of the community building resources available from the various committees. Some examples
  • Community outreach and involvement through Marketing committee venues and jakarta.ee
    • What's New, News
    • Community Announcements
    • Community Events
  • Resource allocation assistance (e.g. additional CI/CD resources anticipated, etc.) from Steering committee
  • General process help from the Specification Committee, etc.)
  • General technical guidance, advice, feedback, review from the Platform Committer team, etc.

Lastly, you are welcome to join any of the weekly Platform Committer team meetings, Tuesday's at 8 AM Pacific. See the Jakarta EE Working Group Calendar for specific details.

[njr-11]

The list of features/changes, would be improved by including issues IDs.

Good idea. I added links.

According to the mentor checklist, the page is improved by including, how to contact the team.

I added this as well.

The mentor checklist asks when Milestone releases will be available -- I presume this means something like a candidate build that other projects or community members could use to assess/work with the proposed changes. Do you have any estimates for that yet?

I'm not the spec lead, just one of the committers helping with getting the plan created, and no, I can't estimate that on behalf of all the other spec participants.

[edbratt]

Thanks! Looks good to go. I will start the ballot.

[edbratt]

Requested updates have been added. Will start ballot