[jakarta.ee-spec.committee] Review for approval: Jakarta EE Specificatio

[Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx>]

The minutes for the March 6th, Specification Committee call are below and are also available here. Please review and be ready for approval during our call on March 20th, 2024. 

Jakarta EE Spec Committee - March 6th, 2024

Attendees (present in bold):

Kenji Kazumura - Fujitsu

Emily Jiang - IBM - Tom Watson

Ed Bratt - Oracle - Dmitry Kornilov

Andrew Pielage - Payara - Petr Aubrecht

David Blevins - Tomitribe - Jean-Louis Monteiro, Cesar Hernandez

Ivar Grimstad - PMC Representative

Marcelo Ancelmo - Participant Member -  Abraham Marin-Perez

Werner Keil - Committer Member

Jun Qian - Primeton Information Technologies - Enterprise Member

Zhai Luchao -  Shandong Cvicse Middleware Co. - Enterprise Member

Guests - Jakarta EE 11 co-release coordinators: Ed Burns, Arjan Tijms

 

Eclipse Foundation: Tanja Obradovic, Wayne Beaton, Paul Buck (chair)

Past business / action items:

• Approval is requested for the minutes from the February 21st, 2024 meeting as drafted - Approved

Agenda:

• Paul Buck is out, Tom Watson is acting as the chair for the March 6th meeting

• Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle

See the spreadsheet for updates.

• [Ivar] Updated plan for Jakarta RESTful Web Services 4.0

• https://deploy-preview-705--jakartaee-specifications.netlify.app/specifications/restful-ws/4.0/

(PR: https://github.com/jakartaee/specifications/pull/705)

• Does the reduced scope warrant a Progress Review?

• Or, can we approve the PR as an adjustment to the current plan?

• It is cleaner to have a progress review.  Can we avoid the overhead and vote here instead?

• We will run the progress review and recommend the project continues with the plan while we vote.

• Ivar sent out a progress review for voting.

• Catch up on the In the Jakarta EE 11 Release Plan, also see Ed Burns recent email to jakartaee-platform-dev:

• https://www.eclipse.org/lists/jakartaee-platform-dev/msg04409.html

• TCK Process situation, see:

• https://www.eclipse.org/lists/jakartaee-platform-dev/msg04406.html

• https://github.com/jakartaee/jakarta.ee/issues/1813

• https://github.com/jakartaee/jakarta.ee/pull/1852#issuecomment-1942131321

• Also see more recently:

• https://www.eclipse.org/lists/jakartaee-platform-dev/msg04410.html

• Jea-320-context

• Questions from Scott Marlow:
  
  On platform-dev, Scott Marlow wrote:
  
  If the Specification Committee needs to make an exception during the Component Specification review to ignore type 3 TCK tests since they cannot deploy on an EE 11 implementation yet, does that mean the Component Specification review cannot really happen until the last EE 11 wave? 
  
  The other question to answer is how to handle restarting the early EE 11 waves if any of the type 3 TCK tests are found to need code changes (note that we don't do service releases during an EE release for minor/major Component Specifications as per Specification Committee discussions in the past).

The component specification projects need to be aware of this requirement as explained in the TCK Process in its most recent version. Suggestion, updated the TCK process to note that these requirements are not applicable to a service release.

The questions from Scott Marlow were discussed 

Action: Emily will respond to these questions in the platform-dev email thread.

[03/06] Check in on proposed clarification (if any) to the Jakarta EE TCK Process

Also see issue “Further clarify the concepts in the 'TCK types and requirements' section of the TCK Process guide” https://github.com/jakartaee/jakarta.ee/issues/1868

Discussed in call, suggest members give it a full review and approve in next committee call.

Discussed versioning of the TCK process.  Suggestion to update to 1.4.1 as a “bug fix” to the text.