MicroProfile Metrics 3.0 Specification Review

[donbourne]

Specification issue template

When creating a specification project release review, create an issue in the MicroProfile-WG repository repo with the content defined as follows.

• Specification name and version: MicroProfile Metrics V3.0
• Add the label Release Review
• Naming conventions for artifacts:
  • Specification PDF in the form of microprofile-project-spec-version.pdf
  • Specification HTML in the form of microprofile-project-spec-version.html
  • project is the microprofile specification short project name (config, health, ...)
  • version is the two digit x.y version of the specification

• The Nexus Staging links (orgeclipsemicroprofile-NNNN where NNNN is the staging repository id) (eg, https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-NNNN/org/eclipse/microprofile/config/) which contain all the binaries and relevant documentation:
  • Staging Repo
  • Spec PDF
  • Spec HTML
  • Javadoc
  • API Jar
  • API TCK Jar
  • REST TCK Jar
  • Optional TCK Jar

• A link in the Eclipse downloads sections is still available for specs and apidocs:
  • https://download.eclipse.org/microprofile/staging/microprofile-metrics-3.0/
  • An apidocs directory containing the javadoc associated with the API jar.

• Summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification.
  • [Compatible Certification Request] (MicroProfile Metrics 3.0 Compatible Certification Request eclipse/microprofile-metrics#623)

• Release Review
  • Follow governance process and create/update release record
    • Component Release Record
  • Email to PMC (more info here)
  • Start release review by emailing EMO (more info here)(Track the bug issue created by EMO after the email)
  • A member of Steering/Spec Committee initiates the ballot by sending an email to [microprofile-wg] (mailto:microprofile-wg@eclipse.org) (more info here
  • Result ballot notification - https://docs.google.com/document/d/1wISp-yRzQZNOHULNekxxg1U18be3v-3CRUswklcpmr8/edit

[aeiras]

hola Don, @donbourne,

we forgot to include the final step, the Result Ballot notification after the initiated ballot is sent.
can you you add the step to Metrics? https://docs.google.com/document/d/1wISp-yRzQZNOHULNekxxg1U18be3v-3CRUswklcpmr8/edit

:) thank YOU! the general template needs to be adjusted as well. :)

[donbourne]

hey Amelia @aeiras , I've added that to the end per your comment.

[aeiras]

Amazing Don, thank you!

[radcortez]

+1

[kwsutter]

@donbourne I just commented on the CCR that the CI used for the testing needs to be a "permanent" artifact and not just a nightly driver that would be difficult to reproduce in the future.

[donbourne]

@kwsutter , we intended for the nightly driver to be stored as a permanent artifact, but messed that up and the driver was deleted. We've rerun the TCK on a newer driver which we're copying for permanent storage and will update the CCR with that URL once it's in place.

[donbourne]

@kwsutter , the problem with the CCR pointing to a non-permanent driver has been resolved. It now points to a downloadable driver that should be there "permanently".

[donbourne]

MP Metrics 3.0 has been released