SmallRye: Compatible Certification Request for MicroProfile OpenAPI 2.0

[phillip-kruger]

• [x] Organization Name ("Organization") and, if applicable, URL:
  Red Hat

• [x] Product Name, Version and download URL (if applicable):
  SmallRye OpenAPI 2.1.0-RC1

• [x] Specification Name, Version and download URL:
  MicroProfile OpenAPI 2.0

• [x] Public URL of TCK Results Summary:
  https://github.com/smallrye/smallrye-open-api/actions/runs/410912721
  

• [x] Java runtime used to run the implementation:
  Java 8 and 11

• [x] Summary of the information for the certification environment, operating system, cloud, ...:
  GH Actions - Ubuntu

• [x] By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.

• [x] By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

[kwsutter]

The Specification Name and Version item should point at the actual Spec. I would put a reference to the eventual maven repo: https://search.maven.org/artifact/org.eclipse.microprofile.openapi/microprofile-openapi-spec/2.0/pom

Same thing for the Compatible Impl. Reference the maven artifact: https://search.maven.org/artifact/io.smallrye/smallrye-openapi/2.1.0-RC1/jar or have the binary available in a download directory that will not be removed. We need a "permanent" location for the CI. And, just to clarify, the version of SmallRye-OpenAPI is 2.1.0-RC1 (vs 2.0.0-RC1 to match the spec)?

[radcortez]

Updated the links.

The version alignment is just a coincidence :)

[dblevins]

These public TCK results are not consumer-friendly and I think we want to do much better in future releases.

Here's the most ideal setup:

• The results summary should be visible on the page itself, not inside a zip. If there are multiple JDKs listed, there is a summary for each one.
• The specification/TCK name and version should be on the same page
• The product name, version and where to download should be on the page.

The page also must be permanent. This looks like output from a CI run still in the CI system and it isn't clear if old builds eventually get removed.

We don't need to fix all of this now, but we should plan to improve things in this area for future releases.

[MikeEdgar]

Completed