[jakarta.ee-spec.committee] Review for Approval: Jakarta EE Specificatio

[Andrew Pielage <andrew.pielage@xxxxxxxx>]

The minutes for the May 13th Specification Committee call are below and are also available here. Please review and be ready for approval during our call on May 27th.

Jakarta EE Spec Committee - May 13th, 2026

Attendees (present in bold):

Kenji Kazumura - Fujitsu - Takahiro Nagao

Emily Jiang - IBM - Tom Watson

Dmitry Kornilov - Oracle, Robert Patrick

Andrew Pielage (chair)  - Payara

David Blevins - Tomitribe - Jean-Louis Monteiro, Cesar Hernandez

Ivar Grimstad - PMC Representative

Arjan Tijms - Omnifish OU - Elected Participant Member Representative 

Werner Keil - Committer Member

Jun Qian - Primeton Information Technologies - Enterprise Member

Zhai Luchao -  Shandong Cvicse Middleware Co. - Enterprise Member

Guest - Jakarta EE 12 co-release coordinators: Jared Anderson, James Perkins

 

Eclipse Foundation: Tanja Obradovic

Past business / action items:

• Approval is requested for the minutes from the April 1st, 2026 meeting as drafted - Approved

Agenda:

• Jakarta EE 12 Update [Jared Anderson]
• Dashboard
• M4 release this Friday
• Not all Core Profile specifications ready for a milestone release
• Other specifications also making milestone releases
• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
• Check on progress of Termination Review for Jakarta Config
• Two-week lazy consensus pre-termination review period started, ending 27th of May
• Check on progress of Termination Review for Jakarta RPC
• Two-week lazy consensus pre-termination review period started, ending 27th of May
• Issue #55 - TCK Archive Format
• Carry over from previous call: MicroProfile are asking for the TCK to not be in a ZIP
• Review previous meeting minutes to determine what was agreed - we were waiting on a PR from Ed
• Are the requirements still the same?
• Discuss where this got to and reassign owner (if appropriate)
• MicroProfile to look at updating how they run the TCK: is a “download” module suitable (e.g. https://github.com/payara/jakartaee-10-tck-runners/blob/EE11/tck-download/jakarta-cdi-tck/pom.xml) 
• The issue we would have, if not, is how to ensure the SHA is the same across the Maven Central versions and Jakarta Downloads
• We will put this on hold until we get some feedback
• Issue #74 - TCK challenge automatic acceptance - [Andrew Pielage]
• Check in on progress of pull requests
• Issue #82 - Consistent approach for TCK challenge exclusions [Andrew Pielage]
• Check in on status of pull request: https://github.com/jakartaee/jakarta.ee/pull/2430 
• Issue #85 - Document Jenkins Maven Publication Jobs [Emily Jiang]
• Carry over from previous call: Needs to be brought up in the Platform call and/or poke projects leads via email. Emily to send an email to the spec leads mailing list.
• Check in on progress
• Email sent today
• New Jakarta EE release process with the new Eclipse Foundation Staging repo [Andrew Pielage]
• Any further action required?
• From our side, seems to be done
• Issue #86 - Simplify Compatibility Certification Requests [Ivar Grimstad]
• Carry over from previous call
• When the CCR for GlassFish 8 comes in Arjan/Ondrej will come with proposals - if no proposals we shall close the issue
• Check in on CCR/proposals - not yet
• Issue #83 Follow-up - Clean Up And Clarify How To List TCK Service Releases On Specification Pages [Andrew Pielage]
• Carry over from previous call: We should draft an example for us to discuss and iterate on, taking into account the easiest way for us to then update all of the changelog files
• https://github.com/jakartaee/specifications/pull/902 
• Discuss any further amendments and actions
• Who is going to maintain the changelog?
• Should the mentor who is promoting the job ensure that a changelog has been updated
• Should we add it to the service release checklist? https://github.com/jakartaee/specifications/blob/master/.github/PULL_REQUEST_TEMPLATE/service_release_pr_template.md 
• If we do, we will need a changelog.md template file (jakarta wombat)
• Andrew to send an email to the spec committee mailing list once the template has been updated
• Sharing Maven Namespaces [Andrew Pielage]
• From previous call: There is some support for defining rules.
• Check in on progress and discuss
• The project is asking for some kind of statement from the spec committee. It would be great if we can formulate something to communicate to them.
• Do we have an opinion?
• Follow the convention until we decide on some rules?
• They are requesting to use `jakarta.ai` as the group ID
• The convention is just jakarta.[shortName]
• At least one voice is suggesting jakarta.ai is too broad
• Concurrency & CDI were using jakarta.enterprise, but have moved away from this
• Is our recommendation that “the Maven groupID should not overclaim the scope of the project”?
• It might be nice to have these “sub-groups”
• For example, we have jakarta.xml for XML-WS and XML-Binding, and jakarta.json for JSON-P and JSON-B
• Should we allow a group to be made before there are any other specifications?
• Does it only make sense to make these groups once two or more specifications exist?
• If they were to follow as-is (current convention): jakarta.agentic-ai
• Would we allow jakarta.ai.agentic? 
• Simple now - map it all out later?
• Recommendation: “The Specification Committee recommends following the existing convention for now of jakarta.${shortName}. Specifications should not overclaim the scope of their project. Namespace groups can be discussed once there are multiple specifications.”
• For this particular case, the recommendation is that the group ID should be `jakarta.agentic-ai`.
• Promoting TCKs is a collective effort
• Carry over from previous call
• Probably worth doing a refresher course when there are more members present
• Can we also document them in our GitHub repo? https://github.com/jakartaee/specification-committee 
• Ivar to take this on - timebox demonstration when we have more time and enough members present
• Ivar to also look for any existing documentation
• We have a tools repository where the scripts exist: https://github.com/jakartaee/specification-tools/tree/master/promotion 
• Various TCKs appear to be failing for EE 11 when ran on Java 25 - some service release fixes incoming
• Review other open issues:
• Determine which issues to label as “enhancement” and add to our board
• Close issues which are no longer relevant or have been dealt with