This email is a reply to https://www.eclipse.org/lists/jakartaee-platform-dev/msg04420.html .
Hello @Nathan
Rauh and the Data specification community.
We discussed this item at the platform call on 2024-02-27. In the days since, I have spoken to the key stakeholders in my capacity as release co-coordinator and I believe this plan is worth pursuing.
-
In order to get buy-in from the broadest and most important set of stakeholders for Data 1.0,
the existing query-by-method-name mechanism must be joined by another query mechanism, call this the "JPQL subset query" mechanism.
-
Given that I judge this buy-in is worth getting, I can entertain a tactical extension of the "start release-review by" date for Data only for the "JPQL subset query" issue and items directly
related to that issue.
-
I judge this schedule extension can be granted in concert with the following conditions.
-
All the stakeholders agree the extension is just to accommodate inclusion of JPQL subset query.
-
The schedule extension is not to be interpreted as open season on new features to make it into 1.0.
-
The schedule extension does not increase the risk of not achieving “June/July EE 11 done”.
-
Data 1.0 is in a unique position to be granted an exception because no other specs depend on it.
-
This plan has the added benefit of increasing the talent pool to allow us to meet the “community chips in” condition GLASSFISH_8_17_21 (see JEA-298).
Specifically, I have been assured by Scott Stark that the inclusion of JPQL subset query will enable Red Hat to make contributions to the Jakarta Data impl for GlassFish.
-
I realize that since the matters in JEA-298 were discussed, the GlassFish community has pushed back on the Java 17 part. This matter is still unresolved.
Thanks for your understanding. Such wranglings are common for 1.0 specs. If anyone wants to hear boring war stories of getting to JSF 1.0
twenty years ago (!) hit me up over some beers at JavaLand.
Ed
