Dry Run - MicroProfile Config 2.0-RC9 - Specification Review

[radcortez]

• Specification name and version
  MicroProfile Config 2.0

• Add a label from one of: creation, plan, progress, release
  Releases

• A link to a directory under https://download.eclipse.org/microprofile/staging in the form orgeclipsemicroprofile-NNN where NNN is the staging repository id assigned to the staged with the following:

  • Specification PDF in the form of microprofile-project-spec.pdf where
    project is the microprofile specification short project name (config, health, ...)
  • Specification HTML in the form of microprofile-project-spec.html
  • An apidocs directory containing the javadoc associated with the API jar.
  • A copy of the staged api jar, and TCK artifact

Instead of a link in the Eclipse downloads section the proposal is to use the Nexus Staging link which contains all the binaries and relevant documentation:

• Staging Repo
  • Spec PDF
  • Spec HTML
  • Javadoc
  • API Jar
  • TCK Jar

A link in the Eclipse downloads sections is still available for specs and api-docs, but is not published anywhere:
https://download.eclipse.org/microprofile/microprofile-config-2.0-RC9/

• Release Review
  • Updated release record
    • Release Record
  • Email to PMC
  • Start release review by emailing EMO
  • Summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification.
    • Compatible Implementation Update API Config RC9
    • Compatible Implementation TCK Run
    • Compatible Implementation TCK Report

[radcortez]

This is just a Dry Run using the proposed template from #193. I know it is not approved yet, but I think we need to try it and adjust it with a real case to see how it goes.

[Emily-Jiang]

We have moved the issue to microprofile-wg.