Kevin walked us through the project board and the “epic issues”.
There is one epic per specification that needs to be updated.
Each epic issue contains a checklist for tasks needed for the release.
If a component specification does not add anything other than what is specified in the overall platform release plan, there is no need to create a release record and engage in a plan review.
Those components adding functionality will need to create a release record on its own.
Discussed the need for progress review. The process does not require this.
Release review ballots must be started for components that are ready as soon as possible.
Committers on individual component specifications are strongly encouraged to help with keeping the status correct in the project tracking board.
Schema namespace needs to be determined and established. (Ivar/Kevin)
Tutorials and Samples will eventually need to be updated to support Jakarta EE 9. (Encourage community involvement.)
API jars must be versioned using major.minor.patch version number. That is three digits. Example: 3.0.0
Back to the top