| [jakarta.ee-spec] Jakarta EE Spec Committee Approved Meeting Minutes - July 27th, 2022 |
Attendees (present in bold):
Kenji Kazumura - Fujitsu
Tom Watson - IBM - Emily Jiang
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 - Martijn Verburg
Werner Keil - Committer Member
Jun Qian - Primeton - Enterprise Member
Zhai Luchao - Shandong Cvicse Middleware Co. - Enterprise Member
Eclipse Foundation: Tanja Obradovic, Paul Buck (chair)
Guests: Scott Stark, Scott Marlow
Past business / action items:
Approval is requested for the meeting minutes from the July 13th, 2022 meeting as drafted - Approved.
Agenda:
Ongoing tracking spreadsheet of individual specs progressing through the JESP
Jakarta EE 10 Release Review - Specifications
Jakarta Concurrency 3.0 TCK situation, need to chose to:
a. Ballot on a resolution to allow an exception to the TCK Process
https://www.eclipse.org/lists/jakarta.ee-spec/msg02673.html
Background: Concurrency was added to the Web Profile for Jakarta EE 10, therefore existing Concurrency tests needed to be added to the Web Profile TCK. The existing Concurrency tests were deployed in EAR files and used remote EJB, neither of which are supported in the Web Profile. The tests in scope here are not new tests, they are existing tests that have been updated to no longer depend on EAR or remote EJB, there is no change to either the functionality or API testing. The Jakarta EE TCK Process states that a "... service release which updates the exclude list MUST not have test additions or updates". Given there are no additions, and the updates have no effect on functionality or API testing, granting the Concurrency project an exception to update their TCK is service release is reasonable.
Resolution: It is resolved that the Jakarta EE Specification Committee grants a Jakarta EE TCK Process exception to the Jakarta Concurrency project to update the tests in their Jakarta Concurrency 3.0 TCK to no longer depend on EAR or remote EJB when executed in environments that does not support these technologies, and deliver these changes as a service release.
Ivar made the motion to go to ballot on the resolution, and it was seconded by Emily.
A notice that the exception was granted was emailed to Concurrency and Platform dev lists
b. Agree that no exception is required
https://www.eclipse.org/lists/jakarta.ee-spec.committee/msg03225.html
Committee has agreed that b. is not a valid option and proceeded to ballot on a.
Continue to review and discuss items to focus on next, see the issues labeled as “enhancement”, other issues are welcome and form the body of our EE 10 Spec Committee retrospective:
Request for Progress Review of Jakarta NoSQL
Assign mentor to walk them through and start ballot
It was noted that there is no Progress Review checklist, some ideas:
Look at their Plan Review including scope
Is there a current:
Milestone Build
Schedule
Version of specification and TCK
Is there a change in Scope?
Progress on a compatible implementation
Ed to create a draft of the Progress Review checklist, and committee members are to review and provide feedback