MicroProfile Health 3.0 Specification Review

[xstefank]

Specification issue template

• Specification name and version
• 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
  • TCK Jar

• A link in the Eclipse downloads sections is still available for specs and apidocs:
  • https://download.eclipse.org/microprofile/staging/microprofile-health-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] (SmallRye: Compatible Certification Request for MicroProfile Health 3.0 eclipse/microprofile-health#279)

• 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 Martin,

We forgot to include the final step, the Result Ballot notification after the initiated ballot is sent.
can 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. :)

[aeiras]

Hola Martin, @xstefank

We forgot to include the final step, the Result Ballot notification after the initiated ballot is sent.
can 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. :)

[xstefank]

PMC approval - https://www.eclipse.org/lists/technology-pmc/msg12125.html. I can't edit the labels. Shouldn't the committers have push rights to this repository?

[Emily-Jiang]

+1! I reviewed all the links and they look good!

[radcortez]

+1 Everything seems ok.

[TetianaFTV]

+1 for Jelastic

[kwsutter]

@xstefank Same comment I made on the Metrics Issue #15... We need the Compatible Implementation to be "permanent" and reproducible. Just pointing at the Metrics code repo is not sufficient. The idea is to have a binary that can be referenced for a long time in case there are ever any questions about whether this Spec, API, CI, and TCK were properly executed and tested.

[xstefank]

Hi @kwsutter, I've released smallrye-health 3.0.0-RC1 - eclipse/microprofile-health#279. Would it be ok like this?

[Emily-Jiang]

Since Kevin is off in the next 4 days, I've checked the build and tck result. I can confirm the build that uses the staged Health 3.0 api was released and all tcks passed. It is ok to proceed with the release. Thank you @xstefank for addressing the issue!

[xstefank]

Thanks @Emily-Jiang. I am going to release MP Health 3.0 now! :)