SmallRye: Compatible Certification Request for MicroProfile OpenTracing 2.0

[xstefank]

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

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

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

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

• [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.opentracing/microprofile-opentracing-spec/2.0

Same thing for the Compatible Impl. Reference the maven artifact: https://search.maven.org/artifact/io.smallrye/smallrye-opentracing/2.0.0-RC1/jar

[xstefank]

@kwsutter updated.

[Emily-Jiang]

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.opentracing/microprofile-opentracing-spec/2.0

@kwsutter This depends on the purpose of this CCR. If we put the unexisting repo as your specified, people won't be able to click the link to verify. This might have defeated the purpose of this CCR. CCR is not the certification proof from my understanding. It is the evidence to prove we can pass all TCKs so we can release the artificates. With what your suggestions, it is like you want this issue hangs around after the release. I think all links should be clickable. I think the link to the relevant repo release tag is the permanent link and it always works even after the push to maven central happens (e.g. https://github.com/eclipse/microprofile-config/releases/tag/2.0)

Same thing for the Compatible Impl. Reference the maven artifact: https://search.maven.org/artifact/io.smallrye/smallrye-opentracing/2.0.0-RC1/jar

[kwsutter]

@Emily-Jiang See my response in the other CCR with the same comment: https://github.com/eclipse/microprofile-fault-tolerance/issues/586#issuecomment-747498547

[dblevins]

Similar feedback as @kwsutter. See my same comment on this CCR https://github.com/eclipse/microprofile-open-api/issues/459#issuecomment-748362004