When creating a specification project release review, create PRs with the content defined as follows.
Include the following in the PR:
- A directory in the form wombat/x.y where x.y is the release major.minor version, and the directory contains the following.
- Specification PDF in the form of jakarta-wombat-spec-x.y.pdf
- Specification HTML in the form of jakarta-wombat-spec-x.y.html
- A specification page named _index.md following the template at: https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md
- For a Progress Review, that sufficient progress has been made on a Compatible Implementation and TCK, to ensure that the spec is implementable and testable.
- For a Release Review, a summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification. The TCK users guide MUST include the instructions to run the compatible implementations used to validate the release.
Instructions MAY be by reference.
- Updated release record
- Generated IP Log
- Email to PMC
- Start release review by emailing EMO
- The URL of the OSSRH staging repository for the api, javadoc:
- The URL of the staging directory on downloads.eclipse.org for the proposed EFTL TCK binary:
- The URL of the compatibility certification request issue:
- Specification JavaDoc in the wombat/x.y/apidocs directory.
If desired, an optional second PR can be created to contain just the JavaDoc in the
apidocsdirectory.
Note: If any item does not apply, check it and mark N/A below it.