Another key decision to allow for continued development efforts.
[KWS] Will need to propose a vote on the mailing list indicating the recommendation of Java SE 8 as the minimum, but we would support both Java SE 8 and 11. (Steve “volunteered” to post the vote.)
Deferred to next meeting
Versioning due to javax.* -> jakarta.*
[KWS] Does the package rename from javax.* to jakarta.* require a major version update for each component spec? For example, does CDI 2.x have to do a 3.0 release when doing the move to the jakarta.* namespace?
We need a target date for the specifications to be ready several weeks before the target end date. Using milestone releases will solve the issue of artifacts timing out in the OSSRH staging repository.
Discussed which implementation will be the first compatible implementation. The optional aspects may “force” this to be Eclipse GlassFish. That means that we will need a release plan for Eclipse GlassFish in order to create a plan for Jakarta EE 9.
[SM] What tasks do we need to do at the platform level for the release?
Discuss on the mailing list.
[IG] Related to the two bullets above: What steps/tasks are needed for a component spec to do the namespace switch?
If we can create such a list, it can be used for the component specs to estimate when they will be able to deliver.