Specifications on Jakarta® EE: The New Home of Cloud Native Java

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

Creation Review PR template

When creating a specification project plan review, create PRs with the content defined as follows.

Link to Specification Project:

Include the following in the PR:

An index page wombat/_index.md following template
Title should be on the form “Jakarta Wombat”

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

Plan Review PR template

When creating a specification project plan 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.
An index page wombat/x.y/_index.md following template
Title should be on the form “Jakarta Wombat X.Y (under development)”
Includes a plan for the release. Usually, a couple of statements is enough. Otherwise, a link to a document describing the release.
Includes a detailed description of any backward incompatibility (Mark with N/A and check if none)
Declares optional features if there are any (Mark with N/A and check if none)
Includes minimum Java SE version
Describe any updates or required changes including splitting out the TCK (Mark with N/A and check if not planned)
Link to updated release record

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

Progress Review PR template

When creating a specification project plan 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.
An index page wombat/x.y/_index.md following template
Title should be on the form “Jakarta Wombat X.Y (under development)”
Specification PDF in the form of jakarta-wombat-spec-x.y-Mn.pdf
Specification HTML in the form of jakarta-wombat-spec-x.y-Mn.html
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.
Link to updated release record

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

Specification PR template

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 apidocs directory.

Note: If any item does not apply, check it and mark N/A below it.

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

specifications

This site is powered by Netlify.

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

Specification Service Release PR template

When creating a service release, create PRs with the content defined as follows.

Include the following in the PR:

The URL of the Eclipse Project release record:
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 (CCR) issue:
Specification JavaDoc in the wombat/x.y/apidocs directory.
Changelog file at this location describing service release updates, wombat/x.y/changelog.
Update wombat/x.y/_index.md accordingly.
Start service release review by emailing Specification Committee and referencing this PR.

Note: Specifications themselves do not have service releases. Only the associated API (limited to JavaDoc updates), JavaDoc, and TCK artifacts can have service releases. Thus, the Specification version does not use the third digit – only the x.y version is used in the Specification directory structure.