Closed Emily-Jiang closed 11 months ago
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.
To be completed by the EMO.
To be completed by the EMO and PMC.
The following applies when the project has a custom website.
To the best of our knowledge:
Things to check:
Required files:
Recommended files:
See examples for Security file and Code of Conduct.
Required elements:
Recommended elements:
To be completed by the EMO
Please consider adding recommended files (i.e. Code of Conduct and Security) directly in each project repository.
Transitive CVEs in MP and Jakarta component specs, that are not addressed yet completely:
The last two of them are Jakarta related and out of scope here, but might require an additional release when fixed there too. For details, see MP Parent issue and comment here.
The EMO review has concluded successfully. Please continue with your release.
SPec Ballot results: MicroProfile 6.1 Ballot has passed
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] 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] A link in the Eclipse downloads sections is still available for specs and apidocs:
[x] Summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification.
[x] Release Review