Re: [jakartaee-platform-dev] [EXTERNAL] Re: Requesting extension for Jak

[Emily Jiang <emijiang6@xxxxxxxxxxxxxx>]

Hi Ed,

On Fri, Mar 1, 2024 at 4:42 PM Ed Burns via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:

On Thu, 29 Feb 2024 23:13:20 +0000 Ed Burns EB wrote:

 

EB> I have spoken to the key stakeholders in my capacity as release co-coordinator and

EB> I believe this plan is worth pursuing.

 

Not only is the plan worth pursuing, the plan is agreed.

 

I request Ivar or Emily, as spec committee members also on this project as committers to advise what action I need to take regarding the spec committee.

 

I think the plan looks reasonable and the team needs to respect the special arrangement and exception and stick to the plan. Since there is no impact to the overall platform release date, I don't think it impacts much. Making the spec committee aware of this special arrangement is fine. I will mention this in the next week's Spec call.

Thanks

Emily

I request anyone who is well enough informed to advise what action I need to take regarding the steering committee.

 

Thanks,

 

Ed

 

| edburns@xxxxxxxxxxxxx | office: +1 954 727 1095

| Calendar Booking: https://aka.ms/meetedburns

|

| Come to JavaLand in Germany on 9 – 11 April 2024 https://javaland.eu

|

| Please don't feel obliged to read or reply to this e-mail outside

| of your normal working hours.

|

| Reply anonymously to this email: https://purl.oclc.org/NET/edburns/contact

 

From: Otavio Santana <otaviopolianasantana@xxxxxxxxx>
Date: Friday, March 1, 2024 at 10:46
To: Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Cc: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>, Ed Burns <Edward.Burns@xxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: Requesting extension for Jakarta Data component specification for EE 11

You don't often get email from otaviopolianasantana@xxxxxxxxx. Learn why this is important

I agree to the conditions.

 

On Fri, Mar 1, 2024 at 3:24 PM Nathan Rauh <nathan.rauh@xxxxxxxxxx> wrote:

As specification co-lead for Jakarta Data, I agree to the conditions specified for granting the extension.

I am copying Otavio, the other co-lead, for his agreement as well.

 

From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Ed Burns via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx>
Date: Thursday, February 29, 2024 at 5:13 PM
To: Jakarta EE Platform Dev List <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Ed Burns <Edward.Burns@xxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] Requesting extension for Jakarta Data component specification for EE 11

This email is a reply to https: //www. eclipse. org/lists/jakartaee-platform-dev/msg04420. html . Hello @Nathan Rauh and the Data specification community. ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍

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

 

 

 

--

Thanks a lot,

Twitter | Linkedin | Youtube

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

--

Thanks
Emily