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

[Andrew Pielage <andrew.pielage@xxxxxxxx>]

The minutes for the August 5th Specification Committee call are below and are also available here. Please review and be ready for approval during our call on August 19th.

Jakarta EE Spec Committee - August 5th, 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 July 8th, 2026 meeting as drafted - Approved

Agenda:

• Jakarta EE 12 Update [Jared Anderson]
• Dashboard
• Platform Minutes
• Rest pending some reviews - M1 releasing soon hopefully
• September 30th for Core Profile unlikely - moving out to 4th quarter
• CDI 5.0 release review pull request up for review - ballot soon
• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
• Check on Progress review for Jakarta Config
• Check on progress of Termination Review for Jakarta RPC
• Two-week lazy consensus pre-termination review period started, ending 27th of May
• Andrew to send termination request to the EMO and PMC
• Issue #74 - TCK challenge automatic acceptance - [Andrew Pielage]
• Check in on progress of pull requests
• 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. Add a checklist item to the spec review checklist
• Emily: I sent this email on July 8th.
• Check in on progress
• Issue #83 Follow-up - Clean Up And Clarify How To List TCK Service Releases On Specification Pages [Andrew Pielage]
• Carry over from previous call: Template is missing
• https://github.com/jakartaee/specifications/pull/902 
• Discuss any further amendments and actions
• PRs merged - issue complete
• Promoting TCKs is a collective effort [Ivar Grimstad]
• 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 
• Tools repository where the scripts exist: https://github.com/jakartaee/specification-tools/tree/master/promotion 
• Timeboxed demonstration when we have time and enough members present
• Todo (ivar): Add a link to the CI instance and job with a couple of bullet points explaining it
• Issue #55 - TCK Archive Format
• Check for any feedback
• On hold for now. Waiting for concrete ask from MicroProfile
• 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
• Issue #89 - SHA512
• Is there any reason why we shouldn’t allow this?
• Issue #48 - Dependency Injection Name
• Nobody is sure what is meant by this. A question has been asked, and we will close next call if we do not get a response.
• Issue #45
• This seems to have been resolved? There was a comment asking if it could be closed two years ago.
• Closing
• https://github.com/jakartaee/specifications/pull/918 
• A question was asked of whether we should allow this in its current state where three milestones are being published (M1, M2, and M3)
• Do we only want to publish the latest?
• Are we happy to just tidy it up when the final release is published?
• Ivar to comment on the pull request that we don’t normally include all milestones, but it’s fine for now (while in development).