| [jakarta.ee-spec] [BALLOT COMPLETE] Progress Review for Jakarta EE 11 |
-1 (Fujitsu)
Because there seems to be no technical reason that Jakarta EE 11 must support JDK17,
we should follow the steering committee’s decision to set the baseline JDK at 21.
Historically, there has been no explicit the alignment policy between Java SE and Java EE/Jakarta EE.
This lack of alignment, while offering a variety options,
has also introduced a degree of confusion and diversity into the Java eco system.
The steering committee’s decision to set a clear direction for all Java stakeholders.
If someone want to use JDK 17, they can just use Jakarta EE 10.
Instead of supporting JDK 17 with Jakarta EE 11,
we should focus on developing and promoting Jakarta EE 11
as a platform for everyone to eager to use JDK 21.
This approach would ultimately strengthen Jakarta EE platform.
-Kenji Kazumura
From: jakarta.ee-spec <jakarta.ee-spec-bounces@xxxxxxxxxxx> On Behalf Of Ivar Grimstad via jakarta.ee-spec
Sent: Wednesday, January 31, 2024 8:00 AM
To: Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>
Cc: Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [jakarta.ee-spec] [BALLOT] Progress Review for Jakarta EE 11
Greetings Jakarta EE Specification Committee,
I request your vote to approve and ratify the updated plan for Jakarta EE 11. This is a joint progress review for the Jakarta EE 11 Platform, Jakarta EE 11 Web Profile, and Jakarta EE 11 Core Profile specifications.
The JESP/EFSP requires a successful ballot of the Specification Committee to approve the plan of this release (as defined in the EFSP).The relevant materials are available here:
The Jakarta EE Platform Project has provided the following motivation for the changes:
This change allows for several things while not restricting anything.
- It allows compatible runtimes to certify on Java SE 17 OR 21, while simultaneously allowing Concurrency to provide Java SE version runtime-aware support for Virtual Threads.
- It allows users who are not at liberty to run Java SE 21 to adopt Jakarta EE 11.
- It allows us to keep our delivery schedule of June/July 2024 to complete Jakarta EE 11.
Per the process, this will be a fourteen-day ballot, ending on Tuesday, February 13, 2024, that requires a Super-majority positive vote of the Specification Committee members (note that there is no veto). Community input is welcome, but only votes cast by Specification Committee Representatives will be counted. According to the process, the ballot will conclude at the earliest on Tuesday, February 6 when all members have cast their vote.
The Specification Committee is composed of representatives of the Jakarta EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Tomitribe, Primeton Information Technologies, and Shandong Cvicse Middleware Co.), along with individuals who represent the EE4J PMC, Participant Members, and Committer Members.
Specification Committee representatives, your vote is hereby requested. Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated.
Thanks,Ivar
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation
Join Community Day for Java Developers - October 16, 2023 (only €40)
EclipseCon 2023 - October 16-19, 2023
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration.