Hello Spec committee,
We consumed a lot of valuable time in the 2024-01-10 meeting on the matter of the Java SE level for EE 11. We discussed this at length in the platform project, in email, in ad hoc meetings, and at the platform project weekly meeting. Here
are the revisions to the EE 11 release plan devised by the platform project. I will copy from the email
archive for your convenience.
-
Platform project keeps the June/July 2024 target for having an EE 11 Ratifying Compatible Implementation.
-
Platform project adjusts JDK compilation requirements:
-
Component spec TCKs and platform TCK must compile under 17.
-
A compatible component impl must pass their component TCK when run under 17 or 21.
-
To ratify a component specification, there must exist an implementation that passes on 17. There must also exist an implementation that passes on 21.
-
These need not be the same implementation. There can be one implementation that passes on 17 and a different one that passes on 21.
-
A compatible platform impl must pass the platform TCK when run under 17 or 21.
-
To ratify a platform specification, there must exist an implementation that passes on 17. There must also exist an implementation that passes on 21.
-
These need not be the same implementation. There can be one implementation that passes on 17 and a different one that passes on 21.
-
This is the same situation as was the case with Jakarta EE 10. For EE 10, it was JDK 11 and 17. For EE 11 it is JDK 17 and 21.
-
Platform project adjusts "release review" targets for component specs: move "release review" targets all out by one month relative to the schedule sent
to Spec Project Leads on 2023-12-13.
-
Wave 1, 2, 3, 4 specs release review by 2024-02-29
-
M2 release
-
Wave 5 specs release review by 2024-03-29
-
M3 release
-
Wave 6, 7 specs release review by 2024-04-27
-
M4 release
-
The key condition to make this plan possible: the GlassFish community is willing and able to deliver an implementation of EE 11 compiled under 17, but passing the platform TCK under 17 and also 21. The release coordinators
expect more community involvement on the Jakarta Data implementation for GlassFish, especially from Red Hat, to achieve this goal.
These changes have been applied to the release plan in PR 822. The
important text is on lines
52 - 64 of the release plan.
Based on what I heard from Wayne in the 2024-01-10 call, no ballot is required for a plan change, because the release review that implements this change will include a vote.
Please let me know if further action is necessary.
Thanks,
Ed and Arjan
Jakarta EE 11 release co-coordinators.
| Reply anonymously to this email:
https://purl.oclc.org/NET/edburns/contact