[jakarta.ee-spec.committee] Follow up on the topic of Jakarta EE 11 Prog

[Emily Jiang <EMIJIANG@xxxxxxxxxx>]

Further to the call yesterday, I understood the committee would like to start a ballot on the EE 11 Progress Review. I did not want to hijack the call to discuss the whole story about the Java 17 support requested. 

IBM intends to vote +1 on the Progress Review. I thought I would provide some more context on our thinking via this note.

When EE 11 plan was made in August 2023, the minimum Java version was set to Java 21 with the hope of the component specifications utilizing the APIs from Java 21. The reality is that none of the specifications used any APIs from Java 21 including Jakarta Concurrency (Jakarta Concurrency does add one method for Virtual Thread, and this does not depend on Java 21.) The Jakarta Concurrency TCK was written in a way that it can pass on either Java 21 or Java 17.

Because of this, the Platform team has agreed with the change of the dependency from Java 21 to Java 17.

What is the consequence of changing the minimum Java version to Java 17?

It has no impact to the runtimes that only plan to support Java 21. They can continue to do so. The only impact is on the specification implementations and ratifying runtimes, and Glassfish has done the necessary updates to support both Java 17 and Java 21.

In order to encourage the widest adoption on Jakarta EE 11, I think it is reasonable to broaden the scope to accommodate Java 17 and the broader set of implementations that run on it. Different runtimes can choose which Java version they support, and this information can be clearly listed on the Jakarta EE compatibility website. It is no change from EE 10, which supports both Java 11 and Java 17.

We think it is important the vote passes, so that we can release Jakarta EE 11 this year. Thank you for spending time reading my note!

Thanks

Emily
================
Emily Jiang

Java Champion, Fellow of BCS

STSM, Jakarta and MicroProfile Architect @IBM

Liberty Cloud Native Architect & Advocate

E-mail: emijiang@xxxxxxxxxx
Twitter: @emilyfhjiang

LinkedIn: https://www.linkedin.com/in/emilyfhjiang/

---

From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of Paul Buck via jakarta.ee-spec.committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Sent: 25 January 2024 03:38
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Cc: Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] [jakarta.ee-spec.committee] Review for approval: Jakarta EE Specification Committee Meeting Minutes - January 24th, 2024

 

The minutes for the January 24th Specification Committee call are below and are also available here. Please review and be ready for approval during our call on February 7th, 2024. Jakarta EE Spec Committee - January 24th, 2024 Attendees (present

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

Report Suspicious

 

ZjQcmQRYFpfptBannerEnd

The minutes for the January 24th Specification Committee call are below and are also available here. Please review and be ready for approval during our call on February 7th, 2024. 

Jakarta EE Spec Committee - January 24th, 2024

Attendees (present in bold):

Kenji Kazumura - Fujitsu

Emily Jiang - IBM - Tom Watson

Ed Bratt - Oracle - Dmitry Kornilov

Andrew Pielage - 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

Guests - Jakarta EE 11 co-release coordinators: Ed Burns, Arjan Tijms

 

Eclipse Foundation: Tanja Obradovic, Wayne Beaton, Paul Buck (chair)

Past business / action items:

• Approval is requested for the minutes from the January 10th, 2023 meeting as drafted - Approved.

Agenda:

• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle

See the spreadsheet for updates.

• In the January 10th Specification Committee call, the situation regarding Jakarta EE 11 Platform Project including Java 17 as a supported platform was discussed. Since that discussion, the Jakarta EE 11 Release Plan was revised:

• See the email from Ed Burns for the background

• https://www.eclipse.org/lists/jakarta.ee-spec.committee/msg03441.html

• Will Lyons shared his observations on this revision with the Specification Committee in his email

• https://www.eclipse.org/lists/jakarta.ee-spec.committee/msg03442.html

• As a follow-up to Will’s email, Wayne Beaton provided his guidance to the Committee in his email

• https://www.eclipse.org/lists/jakarta.ee-spec.committee/msg03444.html

• Today’s agenda topic is for the Committee to review the guidance from Wayne and decide what if any specific actions are required

Options discussed w/ Wayne:

1. Send a warning message noting the plan revision and there is risk to proceeding to Release Review

2. Request a to the Platform Project for Progress Review now noting the changes in the revised plan

3. Do nothing, the Release Review based on this revision is not at risk

The three options were discussed and there are no objections voiced to proceed with option 2. The Spec Committee will therefore initiate a formal Progress Review ballot request for the Platform Project. The committee chair will collaborate w/ the EMO to formulate the request to the Platform Project.

The formal agenda of the committee concluded and a general discussion ensued on Jakarta EE 11 release plan.

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU