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

[Andrew Pielage <andrew.pielage@xxxxxxxxxxx>]

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

Jakarta EE Spec Committee - May 14th, 2025

Attendees (present in bold):

Kenji Kazumura - Fujitsu

Emily Jiang - IBM - Tom Watson

Ed Bratt - Oracle - Dmitry Kornilov

Andrew Pielage (chair)  - Payara - Petr Aubrecht

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

Ivar Grimstad - PMC Representative

Marcelo Ancelmo - Participant Member -  Abraham Marin-Perez

Werner Keil - Committer Member

Jun Qian - Primeton Information Technologies - Enterprise Member

Zhai Luchao -  Shandong Cvicse Middleware Co. - Enterprise Member

Guest - Jakarta EE 11 co-release coordinators: Ed Burns, Jared Anderson

 

Eclipse Foundation: Tanja Obradovic

Past business / action items:

• Approval is requested for the minutes from the April 30th, 2025 meeting as drafted - approved

Agenda:

• Catch up on the Jakarta EE 11 Release Plan [Ed Burns]
• EE 11 - Prioritized backlog · Jakarta EE11 TCK Release (github.com) and Jakarta EE11 TCK Release board  
• Tentative schedule thoughts
• May 21 TCK complete
• June 5 CCR created and mentor review started
• June 9 start ballot (complete 7 to 14 days)
• Three issues blocking GlassFish being used for CCR
• Should be easy to fix
• Catch up on the Jakarta EE 12 Release Plan [Jared Anderson]
• Project board: https://github.com/orgs/jakartaee/projects/17/views/1 
• Only waiting on Activation now - all other ballots complete or in progress
• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
• Issue #55 - TCK Archive Format [Ed Bratt]
• Check in on Ed Bratt’s PR: pending
• Issue #83 - Clean up and clarify how to list TCK service releases on spec pages
• Check on progress of pull requests
• Issue #74 - TCK challenge automatic acceptance
• Check on progress of specifications
• Spec Committee still required to send emails out
• Platform project also encouraging responses
• What timeframe should we give for them to choose? May 16th is now very close and most specifications have been emailed.
• In the case of lazy acceptance, how do we add the necessary labels? 
• Committer access required
• How do we prevent bad actors?
• Issue #58 - TCK challenge templates [Andrew Pielage]
• Check on progress of pull requests
• Issue #82 - Consistent approach for TCK challenge exclusions [Ed Bratt]
• Carry over from February 19th: TCK Process should be updated with something akin to Scott Starks suggestion.
• 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

--

Andrew Pielage
Senior Software Engineer

		payara.fish
		+448005385490

Try our fully managed cloud native application runtime. 15 day trial available. Payara.cloud

Payara Services Ltd, Registered office: Malvern Hills Science Park, Geraldine Road, Malvern, WR14 3SZ, United Kingdom
Registered in England and Wales: 09998946 | VAT: GB 193854467

Payara is a proud recipient of the prestigious Queen's Award for Enterprise: International Trade 2021