deliver Platform milestone artifacts for Jakarta EE 9

[kwsutter]

Signed-off-by: Kevin Sutter kwsutter@gmail.com

Specification PR template

When creating a specification project release review, create two PRs with the content divided as follows.

Include the following in PR#1:

• 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 wombat-spec-x.y.pdf
• Specification HTML in the form of 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.
• The URL of the OSSRH staging repository for the api, javadoc:
  https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/platform/jakarta.jakartaee-api/9.0.0-RC2/
• The URL of the staging directory on downloads.eclipse.org for the proposed EFTL TCK binary:
  
• The URL of the compatibility certification request issue:
  

Include the following in PR#2:

• Specification JavaDoc in the wombat/x.y/apidocs directory.

[netlify]

Deploy preview for jakartaee-specifications ready!

Built with commit 64ba008

https://deploy-preview-180--jakartaee-specifications.netlify.app

[smillidge]

If you are collecting issues for later. Most of the diagrams need replacing and updating to the latest names.

[kwsutter]

If you are collecting issues for later. Most of the diagrams need replacing and updating to the latest names.

Definitely! We started that exercise with the charts in the Deployment section. We recreated them as svg using inkscape. Now they are easily editable. We need to do this with the other diagrams as well. Documented via this Issue.