Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dry Run - MicroProfile Config 2.0 Specification Review #195

Closed
14 tasks
radcortez opened this issue Nov 5, 2020 · 1 comment
Closed
14 tasks

Dry Run - MicroProfile Config 2.0 Specification Review #195

radcortez opened this issue Nov 5, 2020 · 1 comment

Comments

@radcortez
Copy link
Contributor

  • Specification name and version

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

  • 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: (Does not apply to creation/plan review lifecycle events.)
    (micropfile-config, microprofile-health, ...) and x.y is the release major.minor version, and the directory contains 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
  • For a Release Review:

    • Updated release record
    • Generated IP Log (For the microprofile platform release)
    • 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.
  • For a Progress Review, that sufficient progress has been made on a Compatible Implementation and TCK, to ensure that the spec is implementable and testable.

@radcortez
Copy link
Contributor Author

Duplicate of #196. GH gave me a 404 and it seems that it duplicated the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant