| [jakarta.ee-spec.committee] Review for approval: Jakarta EE Specification Committee Meeting Minutes - February 21 st, 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 7th, 2023 meeting as drafted - Approved.
Agenda:
Ongoing tracking spreadsheet of specifications progressing through the JESP specification version lifecycle
See the spreadsheet for updates.
Catch up on the In the Jakarta EE 11 Release Plan, also see Ed Burns recent email to jakartaee-platform-dev:
Spec are tracking to the EE 11 release plan, starting with specs in waves 1 through 4
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.
JAX B optional (really meaning removed from EE 11) disgruntlement and surprise.
The current situation with JAX B was discussed and it was noted:
The following resolution was approved in the February 8th, 2023 Specification Committee call
“An individual specification can have optional features, however when a component specification is included in the Platform and Web Profile, and Core Profile an optional feature must be explicitly declared as required, otherwise it is not required. This requirement is noted in the Platform specification.”
The ballot result was published in the February 8th, 2023 meeting minutes and on the public jakarta-ee-spec mailing list:
Does the Specification Committee need to do more to communicate process changes to specification projects?
Suggestion: Release Coordinator to call out at the start of the release what process updates have happened since the last release and are applicable to the current release.
Action: Also, chair to create a tracking issue to remind the committee to explore ways to more effectively communicate its resolution and make them easier to find/discover.