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

[Andrew Pielage <andrew.pielage@xxxxxxxx>]

The minutes for the October 14th Specification Committee call are below and are also available here. Please review and be ready for approval during our call on October 28th.

Jakarta EE Spec Committee - October 14th, 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 September 30th, 2026 meeting as drafted - Approved

Agenda:

• Jakarta EE 12 Update [Jared Anderson]
• Dashboard
• Platform Minutes
• REST hopefully out by the end of the week
• Core Profile in 4 weeks in danger
• Ballot on Authorization moving to Web Profile passed
• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
• Jakarta CRaC Creation Review
• Passed!
• Check on Progress review for Jakarta Config
• >From previous calls:
• Ondrej is aware of the need for a progress and is looking to submit one after the summer holidays: https://www.eclipse.org/lists/config-dev/msg00275.html 
• A Jakarta Future Directions call may touch on this as the namespace is a topic on the agenda (24th Sep)
• Project Lead needs updating - Dmitry not working on it any more
• Emily also a project lead
• Spec is still stuck at the point of “if MicroProfile Config moves to Jakarta then there’s no need for a separate Jakarta Config”.
• Check on progress of Termination Review for Jakarta RPC
• Carry over from previous call: check up on termination review 
• Eclipse GitLab appears to be down
• Issue #74 - TCK challenge automatic acceptance - [Andrew Pielage]
• Check in on progress of pull requests
• Carry over from previous call 
• Emily to create a PR to expand the final “Filing a Certification Request” bullet point
• Not created yet
• Issue #89 - SHA512 - [Andrew Pielage]
• Check in on progress of pull requests
• 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
• CDI CI job was publishing to the Download area, bypassing certificate signing
• Not sure where they got the permissions from
• If it was inherited from the parent pom, there is a new version all specifications will have to move to anyway
• We need to review where it got the permissions from and check it is resolved.
• Issue #39 - Project Handbook States Service Releases Require Release Reviews
• Carry over from previous call
• Emily/Ivar to bring it up on the TAC
• Check in on progress - have we handed it over?
• There hasn’t been a TAC yet - there might be one next week
• Issue #27
• Carry over from previous call
• Would require assistance from the web dev team - we can’t just add that status
• We need to file an issue to get this addressed and work on it in tandem: https://github.com/jakartaee/jakarta.ee 
• Assign an owner
• No volunteers
• There is a new version of the specification pages coming out very shortly
• We can review on the next call if this is still relevant.
• 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 #22
• No clarifying update on the one outstanding item - can we move to close?
• Nobody on the call voiced an opinion on it being required
• Look to close next call if nobody voices dissent.
• Issue #14
• Nobody on the call has any opinions.
• Look to close next call if nobody voices dissent.
• Issue #8
• The process diagram linked no longer seems to exist on master/main
• A historical record of it can be found here: https://github.com/jakartaee/specification-committee/blob/7f9948bff6db1711d649610db02671266b705fd7/TCKProcess.png 
• So we have TCK challenge templates, but the labels are not automatically applied on all templates.
• It should be possible to get the labels added as a part of the template
• This may have been address in https://github.com/jakartaee/specification-committee/issues/58 aside from any outliers.
• So the remaining item is whether we want to use project boards.
• We would need a board for every project, similar as to how we had to create a PR template for every project
• We could alternatively have an organisation-level board to track all challenges
• Is there anyone on the call that feels the boards are necessary or useful?
• The main issue is challenges actually being addressed
• Specifications could maintain their own boards if they wish
• Do we feel like it needs to be a mandate?
• Silence
• We will look to close this as done on the next call unless there is any new opinions shared.
• We say farewell to Werner! He can be found on Platform and other specifications
• Nathan takes over the committer rep role
• DST changes next call for those outside of the states (and those that follow similar timings).
• The call will be one hour “earlier” for those in the UK and Europe
• Jakarta EE open call next Tuesday (check the shared community calendar and mailboxes).
• Jakarta EE Community Open Call