Since we're running and passing the official Jakarta CDI 3.0 TCK we can file a certification request and get OpenWebBeans listed as a compatible implement on this page:
- https://jakarta.ee/specifications/cdi/3.0/ If we update our CDI 2.0 TCK from the JBoss version to this one we can also get listed on the Jakarta CDI 2.0 page: - https://mvnrepository.com/artifact/jakarta.enterprise/cdi-tck-impl/2.0.7.SP1 The primary thing we need to do that is new is create a "Public TCK Results Summary" page on our website for this OWB version and TCK version. This could be on our actual download page if we wanted. That data we need to show is: - Product Name, Version and download URL (already on the download page) - Specification Name, Version and download URL - TCK Version, digital SHA-256 fingerprint and download URL - Java runtime used to run the implementation - Summary of the information for the certification environment, operating system, cloud, … - List of tests passed (can be a link to another page, say the xml output from running the TCK) My recommendation is that we find a way to do this on the download page in a short addition to the 2.0.22 section. It's quite perfect that the download page is not a table, so it'll be easy to sneak in the extra info. I think we can get it done in a sentence or two and a link to the TCK results. After the release is up and we've put the above information somewhere on our site we then 1) file an issue in the CDI spec project labeled 'certification' and wait for an approval or for the approval period to timeout. Once it's been approved we send an email to t...@eclipse.org with a link to the approved issue. I wrote a lot of this process so I'm happy to do the first one if someone can point me to instructions on how to update the website. Here's the full documentation on the process: - https://jakarta.ee/committees/specification/tckprocess/ -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com
smime.p7s
Description: S/MIME cryptographic signature
