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

[Andrew Pielage <andrew.pielage@xxxxxxxxxxx>]

The minutes for the February 4th Specification Committee call are below and are also available here. Please review and be ready for approval during our call on February 18th.

Jakarta EE Spec Committee - February 4th, 2026

Attendees (present in bold):

Kenji Kazumura - Fujitsu - Takahiro Nagao

Emily Jiang - IBM - Tom Watson

Ed Bratt - Oracle - Dmitry Kornilov

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 January 7th, 2026 meeting as drafted - Approved

Agenda:

• Jakarta EE 12 Update [Jared Anderson]
• Dashboard
• Delays to the final EE 12 release are in discussion, ideally keeping it within the year
• Platform release still drives the component specifications (top-down)
• Adoption of implementation of individual specifications are requested by other frameworks and techs, such as Quarkus, Helidion, Spring, etc. without them being part of a platform release. This in itself has value even if customers aren’t specifically asking for a platform release right now
• There is a new staging repository for artifacts: https://repo3.eclipse.org/#browse/browse:ee4j-staging 
• Progress being made with the OSSRH issues
• One issue remaining
• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
• Carry over from previous calls:
• Progress reviews for Jakarta Config and RPC overdue.
• Jakarta Config approaching two years overdue
• A Jakarta Futures meeting will happen tomorrow and will be discussing MicroProfile Config and Jakarta Config
• Jakarta RPC approaching three years overdue
• Oracle to be poked before contacting the EMO
• Issue #55 - TCK Archive Format [Ed Bratt]
• Check in on Ed Bratt’s PR: pending
• Issue #74 - TCK challenge automatic acceptance - [Ed Bratt]
• Check on progress of specifications - set as a goal for M2
• Issue #58 - TCK challenge templates [Andrew Pielage]
• Check on progress of pull requests - set as a goal for M2
• 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.
• Issue #85 - Document Jenkins Maven Publication Jobs [Emily Jiang]
• Specifications having wiki pages (or equivalent documentation) goal for M2
• Carry over from previous call: Needs to be brought up in the Platform call and/or poke projects leads via email
• Issue #86 - Simplify Compatibility Certification Requests [Ivar Grimstad]
• Carry over from previous call
• Example to be created
• Ivar to reach out to understand the complaints
• Issue #83 Follow-up - Clean Up And Clarify How To List TCK Service Releases On Specification Pages
• Carry over from previous call: An issue to be created for further discussion [Ivar]
• Discussions ongoing on how to track changes between TCK service release versions
• There’s already a changelog file they can update, it’s just not mentioned on the PR template file
• https://github.com/jakartaee/specifications/blob/master/service_release_pr_template.md vs. https://github.com/jakartaee/specifications/blob/master/.github/PULL_REQUEST_TEMPLATE/service_release_pr_template.md 
• It needs to be clear which changes are for the API service releases vs. the TCK service releases
• Changelogs are already versioned by the major/minor specification version e.g. https://github.com/jakartaee/specifications/blob/master/jsonp/2.1/changelog.md 
• We could have headings for API and TCK which the releases would be listed under (most recent release at the top).
• 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
• Committee members
• Please confirm committee members participants and for the strategics alternates as well, as documented on https://jakarta.ee/committees/specification/
• Please make Pull Requests to https://github.com/jakartaee/jakarta.ee/ 
• Suggestion: Add committee members photos on the above page; please confirm you are all in agreement with the suggestion
• Individuals can opt out
• Use the pictures already added to Eclipse accounts
• Likely use a more compact format than that used on project “Who’s Involved” page

Committee meeting requirements cheat sheet added to bottom of agenda doc and circulated in the mailing list.

--

Andrew Pielage
Senior Software Engineer

		payara.fish
		+448005385490

Deploy your Spring, Quarkus, and Jakarta EE apps in seconds with Payara Qube. Try FREE

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