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

[Andrew Pielage <andrew.pielage@xxxxxxxxxxx>]

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

Jakarta EE Spec Committee - January 22nd, 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 January 8th, 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  
• TCK work continues
• Web Profile ballot completion delivery date still Q1
• Platform Q2
• Catch up on the Jakarta EE 12 Release Plan [Ed Burns]
• Reza drafted an action plan
• EE 12 label has been added to the issues
• Security Manager API to be removed
• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
• Check on Progress Reviews for:
• Jakarta NoSQL 
• https://jakarta.ee/specifications/nosql/
• https://www.eclipse.org/lists/jakarta.ee-spec/msg02795.html [Progress Review, 10.2022]
• Issue for progress review created: https://github.com/jakartaee/nosql/issues/185
• Some activity on the issue, finishing off the TCK
• Jakarta Config 
• https://jakarta.ee/specifications/config/
• https://www.eclipse.org/lists/jakarta.ee-spec/msg02838.html [Plan Review, 01.2023]
• Issue for progress review created: https://github.com/jakartaee/config/issues/277 
• No update yet
• Jakarta RPC 
• https://jakarta.ee/specifications/rpc/
• https://www.eclipse.org/lists/jakarta.ee-spec/msg02129.html [Creation Review, 01.2022]
• Issue for progress/plan review created: https://github.com/jakartaee/rpc/issues/3 
• No update yet
• Check on Creation Review for Jakarta Logging
• Christian has been asked to create the Creation Review pull request
• Clean up and clarify how to list TCK service releases on spec pages
• Carry over from last call
• Suggestion:
• Add an extra bullet point with text along the lines of “For all TCK releases, see download directory here)” and link to the download directory for that version of the specification (e.g. https://download.eclipse.org/jakartaee/servlet/6.1/)
• Extra suggestion: only add this text once there has been a service release made?
• No
• Should there be an announcement for when service releases are published? The page itself would no longer be getting updated
• All versions are valid
• No
• Action: Specification mentors to create pull requests to https://github.com/jakartaee/specifications to update their pages
• Action: Ivar to update the template: https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md 
• Action: Andrew to create an issue to track
• Issue #55
• Check in on Ed Bratt’s document: link
• Check in on Ed Bratt’s PR: pending
• Issue #74
• Email: https://www.eclipse.org/lists/jakarta.ee-spec.committee/msg03564.html 
• Feedback: deadline to apply would be March 1st instead of April 1st
• Question: Do we need to apply this to each individual specification, or just to the TCK process?
• Currently the TCK Process is not normative - only the individual user guides are
• Should we also add the challenge acceptance strategy to the TCK challenge template? https://github.com/jakartaee/platform/blob/main/.github/ISSUE_TEMPLATE/tck_challenge.md 
• Feedback: some objection to adding challenge text to the specification GitHub readmes
• We could also add it as a standalone “challenge” file at the top-level of the GitHub repositories alongside the readme, code of conduct, license etc.
• Discussion to continue in the mailing list or on the GitHub issue for resolution next call
• Issue #58
• This is not strictly with Emily, pull requests using the template just need to be made
• Issue #81
• No issues found - can proceed
• 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