Re: [jakartaee-tck-dev] EE 11 Platform TCK Status update to Steering com

[Ed Burns <Edward.Burns@xxxxxxxxxxxxx>]

Hello,

 

We talked through the so-called “10 + 11” proposal at the Steering Committee today.  Here is a list of suggested changes:

 

• Remove “ratifying” from “ratifying compatible implementation”.
• Clearly commit to producing an EE 11 TCK that does not have this hybrid approach.
• Do not overload the term “EE 11 TCK”.
• Instead, define the EE 11 TCK as
• “11 with exclusions” and “10 with a different set of exclusions”

 

Here is the revised plan for the delivering the Jakarta EE 11 Web and Platform TCK in time for the Web and Platform ballots to start no later than 2024-11-18.

 

The Jakarta EE 11 Web and Platform TCK will consist of

1.      A sufficiently complete, refactored, Web and Platform TCK using the new system devised by the Platform TCK project team.

a.      An exclusion list of tests the Platform TCK project deems can be safely excluded without sacrificing compatibility coverage given the other provisions of this plan.

2.      A version of the Jakarta EE 10 TCK designed to certify EE 11 compatible implementations on the required Java versions for Jakarta EE 11.

a.      An exclusion list of tests the Platform TCK project deems can be safely excluded without sacrificing compatibility coverage given the other provisions of this plan.

3.      A TCK User Guide describing how to run the previous two parts.

 

Taken together, the two exclusion lists is to provide an acceptable amount of compatibility assertion so that voting members can feel confident in voting to approve the EE 11 Web and Platform ballots.

 

Otherwise, the usual rules for compatible implementations will still apply.

 

Finally, the Jakarta EE Platform and Platform TCK projects commit to delivering a version of the Jakarta EE 11 Web and Platform TCK that does not require the use of a Jakarta EE 10 TCK as the first deliverable after the delivery of EE 11.

 

Thanks,

 

Ed

 

 

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

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

|

| 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: Ed Burns
Sent: Tuesday, October 22, 2024 12:26 PM
To: Jakarta EE Platform Dev List <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>; jakartaee-tck-dev@xxxxxxxxxxx; Jakarta EE Steering Committee <jakarta.ee-steering@xxxxxxxxxxx>
Subject: EE 11 Platform TCK Status update to Steering committee

 

Please pardon the wide distribution. I request that any replies to this thread happen on the Platform Dev list or directly to me, and I will forward any individual responses to the Platform Dev list.

 

Greetings programs and committees via Cc.

 

Consider this an out-of-band status update to my update at the Steering Committee meeting on Tuesday 2024-10-15. At that meeting, I stated:

 

• The Platform Project is re-evaluating the ability to deliver EE 11 in time for the ballots to complete in time for JakartaOne on 2024-12-03.
• We are confident to be able to do this for the Core Profile.
• We are not as confident to do this for the Web and Platform profiles.

 

Here is the update I gave at the Spec Committee on Wednesday 2024-10-16 , with Scott Stark present and representing the Platform TCK project:

 

 

The Platform TCK Team did some estimating, with the following changes:

 

• Assume <stakeholder consented estimating exercises from 2024-10-16 Platform TCK call (See agenda)>
• With these changes, we got to GF passing 84%.
• For discussion let's call this the "11 with exclusions" proposal.
• We propose to exclude the remaining 16%
• produce a list of those excluded tests, and let the stakeholders decide.
• It is likely that the big portion of those excluded tests are appclient tests.
• The Platform TCK team discussed several options for producing an offer with a high likelihood of acceptance by the voting stakeholders of the Spec Committee but put them aside in favor of the "11 with exclusions" proposal.
• Discussion at the Spec Committee revealed that the "11 with exclusions" proposal does not have a high likelihood of acceptance by the voting stakeholders of the Spec Committee.
• Ed revived one of the "put aside" proposals from the Platform TCK Team.
• For discussion let's call this the "10 + 11" proposal.
• To be a ratifying compatible implementation of the Jakarta EE 11 Platform and Web Profiles, an implementation must:
• Pass the Jakarta EE 11 Platform TCK according to the "11 with exclusions" proposal.
• Pass the off-the-shelf Jakarta EE 10 Platform TCK, but with a well-defined set of exclusions, as defined by the Jakarta EE Platform Project team and TCK team.

 

Here is the update I am giving you now:

 

The Jakarta EE Platform Project team and TCK team believes the above "10 + 11" proposal is the most likely way to deliver EE 11 in time for the ballots to complete in time for JakartaOne on 2024-12-03.

 

Thanks,

 

Ed Burns

Jakarta EE 11 co-release coordinator

 

 

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

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

|

| 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