Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] [External] : [BALLOT] Progress Review for Jakarta EE 11

-1, Oracle

  • At the outset of EE 11 we agreed that it was important for Jakarta EE to get back to releasing on and utilizing features of the current LTS JDK. Oracle still believes this is an important goal.
  • The proposal before us suggests we are not achieving the goal to leverage Java 21 (only one Spec. appears to be utilizing specific JDK 21 features).
  • Releasing EE 11 without (or minimally) leveraging features of the latest JDK will inevitably delay the EE release that does leverage current JDK features, further undermining the the initial goal. 
  • At our current pace the next EE release (Jakarta EE 12, estimated release in 2026) will likely be delivered 3 years after JDK 21. That seems very late to us and could undermine any competitive advantage EE might be able to attain.
  • Rather than releasing to an artificial deadline, Oracle would prefer that we assess our progress and determine what can be done to better achieve the original goal. If this requires a delay, we would prefer that option.
  • Lastly, this change increases the workload of the TCK efforts since all TCKs will need to be tested twice (on JDK 17 and on JDK 21) prior to being released.

Thank you,

-- Ed Bratt

On 1/30/2024 3:00 PM, Ivar Grimstad via jakarta.ee-spec wrote:
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


_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec__;!!ACWV5N9M2RV99hQ!IoxLTbog-e0DgvO-4efzSYXeX9DNcreMQE_h_zU2O0EyDENac0o9XEsS8GBYd4bafoR_8Mb3Xk9rD8dcGo1NR-P_eP0$

Back to the top