Date: 2020-01-28
Present:
Alternatives (https://www.eclipse.org/lists/jakartaee-platform-dev/msg01400.html):
Support for Jakarta EE 8 and earlier schemas is optional in Jakarta EE 9 products. Votes: 0
Support for Jakarta EE 8 and earlier schemas is required in Jakarta EE 9 products. Votes: 0
Support for Jakarta EE 8 but not earlier schemas is required in Jakarta EE 9 products; support for schemas earlier than Jakarta EE 8 is optional in Jakarta EE 9 products. Votes: 7
DECISION: Option #3 is the desired direction. Need to widely communicate to the community. Also need to update Platform Spec accordingly. Steve volunteered to start a PR for the Platform Spec.
Discussed: TCK compatibility rule or included in specification? Raise to specification committee?
Decided to treat it as a TCK compatibility item, and not included in the specification. Bill will draft a TCK rule to cover this case.
Must be communicated to the TCK team that the TCK must work on both JDK 8 and 11. Different signature files must be generated for 8 and 11.
https://github.com/eclipse-ee4j/glassfish-spec-version-maven-plugin/issues/14
Until this bug has been fixed, it is ok to comment out the plugin to be able to release RCx versions, e.g. 1.0.0-RC1.
Should this and other plugins move to this project from GlassFish?
The target project must have committers able to work on the plugin. Suggestion to create a Jakarta Tools project for the plugins and tools. A lot of these are currently in the GlassFish project. Decided to move this discussion to the PMC. Ivar will add it to the PMC’s agenda.
Kevin will check with David. (done)
Need a release plan for EJB 4.0 by Feb 1.
Need basic API updates for Glassfish.
And, need corresponding changes for TCK.
Encourage projects to identify tasks with labels indicating which are easy to grab for community members.
Use the next Jakarta Update call to give a “getting started guide”. Invite Ambassadors and other community members.