MicroProfile Metrics 5.1 Specification Review

[Emily-Jiang]

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.

• [x] Specification name and version

• [x] Add the label Release Review

• [x] Naming conventions for artifacts:

  • [x] Specification PDF in the form of microprofile-project-spec-version.pdf
  • [x] 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

• [x] 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:

  • [x] Staging Repo
  • [x] Spec PDF
  • [x] Spec HTML
  • [x] Javadoc
  • [x] API Jar
  • [x] API TCK Jar Optional TCK Rest TCK

• [x] A link in the Eclipse downloads sections is still available for specs and apidocs:

  • [x] https://download.eclipse.org/microprofile/staging/microprofile-metrics-5.1.0/
  • [x] An apidocs directory containing the javadoc associated with the API jar.

• [x] Summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification.

  • [x] [Compatible Certification Request] (https://github.com/eclipse/microprofile-metrics/issues/791)

• [ ] Release Review

  • [x] Follow governance process and create/update release record
  • Component Release Record
  • [x] Email to PMC (more info here)
  • [x] Start release review by emailing EMO (more info here)(Track the [bug issue](add link) created by EMO after the email)
  • [x] A member of Steering Committee initiates the ballot by sending an email to [microprofile-wg] (mailto:microprofile-wg@eclipse.org) (more info here
  • [x] After the voting has ended, email [microprofile-wg] (mailto:microprofile-wg@eclipse.org) with the ballot result (more info here

[mtdelgadoa]

We're updating our release review process by integrating the review checklist directly into your GitHub workflow. This change will enhance our ability to provide more effective feedback within the context of each issue, leading to improved efficiency, collaboration, and the elimination of duplication.

EMO REVIEW

• PMI Review Record: link

Intellectual Property Management

To be completed by the EMO.

• [ ] All project code has copyright and license headers correctly applied. EMO will scan the code at their discretion
• [x] All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)

Open Source Rules of Engagement

• [x] PMC approval on the mailing list

Branding and Trademarks

To be completed by the EMO and PMC.

The following applies when the project has a custom website.

To the best of our knowledge:

• [x] Project content correctly uses Eclipse Foundation trademarks
• [x] Project content (code and documentation) does not violate trademarks owned by other organizations

Things to check:

• Project website uses the project's formal name in first and all prominent references
• Project website includes a trademark attribution statement
• Project website footers contain all necessary elements

Legal Documentation

Required files:

• [x] License files in all repository roots
• [x] README
• [x] CONTRIBUTING (or equivalent)

Recommended files:

• [x] NOTICES or equivalent you can use the Legal Documentation generator available under committer tools
• [ ] CODE_OF_CONDUCT
• [ ] SECURITY

See examples for Security file and Code of Conduct.

Required elements:

• [x] ECA is referenced/described

Recommended elements:

• [x] Build instructions provided
• [ ] Security policy is described

Metadata (PMI)

To be completed by the EMO

• [x] The formal name, e.g. "Eclipse Foo™", is used in the project title
• [x] The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
• [x] The project description starts with a single paragraph that can serve as an executive summary
• [x] Source code repository references are up-to-date
• [x] Download links and information are up-to-date (see EF handbook for more information on how-to do this)
• [x] Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)

[mtdelgadoa]

Please consider adding recommended files (i.e. Code of Conduct and Security) directly in each project repository.

[mtdelgadoa]

The EMO has concluded this review. Please continue with your release.

Spec Ballot results: https://www.eclipse.org/lists/microprofile-wg/msg02241.html