| [jakarta.ee-spec] Jakarta EE Spec Committee Approved Meeting Minutes - March 20th, 2024 |
Jakarta EE Spec Committee - March 20th, 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 March 6th, 2024 meeting as drafted - Approved.
Agenda:
Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
Check in on EE 11 Release Review ballots, see the spreadsheet for updates and notes.
Catch up on the Jakarta EE 11 Release Plan [Ed Burns]
TCK Process situation, see:
https://www.eclipse.org/lists/jakartaee-platform-dev/msg04406.html
https://github.com/jakartaee/jakarta.ee/pull/1852#issuecomment-1942131321
Also see more recently:
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.
[03/20] Follow-up on review and approval of proposed clarification (see above). There were no objections to proposed clarification as documented in the pull request ( https://github.com/jakartaee/jakarta.ee/pull/1869). Therefore it was approved as written in PR 1869. The clarification took effect when approved on 03/20/2024 at 9:18AM PT. The PR can be merged.
[Late addition on the agenda] The topics described in this email https://www.eclipse.org/lists/jakarta.ee-spec.committee/msg03478.html were discussed in the call. It was proposed that publishing to Maven Central with the project license is acceptable. Note that given that the EFTL is not included in the file, the SHA and SIG sums would not be valid. Further investigation is needed. Topic to be revisited in the next committee call.