Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Implementation Certification Process"
m |
m |
||
| Line 7: | Line 7: | ||
# If runtime wants to be added to [https://start.microprofile.io/ MicroProfile Starter], please raise [https://github.com/eclipse/microprofile-starter/issues an issue] and propose a PR there. | # If runtime wants to be added to [https://start.microprofile.io/ MicroProfile Starter], please raise [https://github.com/eclipse/microprofile-starter/issues an issue] and propose a PR there. | ||
| − | [[Category | + | [[Category:MicroProfile]] |
Revision as of 14:35, 26 January 2024
Below are the steps that ought to be followed when a runtime (member of the Working Group or not) certifies against a particular MicroProfile release:
- Follow the MicroProfile TCK Process to file a Compatible Certification Record (CCR) in the MicroProfile GitHub repo.
- After the certification issue is accepted, file a Marketing GitHub issue [1] with the label of Compatibility using the issue template named New Compatible Implementations To be Added.
- If runtime wants to be added to MicroProfile Starter, please raise an issue and propose a PR there.