Replying to my own email.
 
My thought is to add a link on the sidebar of the website for Compatibility by editing
https://github.com/eclipse-ee4j/glassfish/blob/master/docs/website/src/main/resources/_config.yml
 
Point this at a root page which lists the compatibility statements preceded by some boiler plate intro text and a link to each statement and results. That way each specification that wants to use GlassFish as the compatible implementation
 can create a PR to add their statement documentation and update the root page.
 
Thoughts?
 
Steve
 
From: Steve Millidge (Payara)
Sent: 31 July 2019 10:01
To: 'glassfish developer discussions' <glassfish-dev@xxxxxxxxxxx>
Subject: RE: Hosting TCK results
 
 
 
Hi All,
 
I didn’t get much response from this request. So to kick it off again. As a compatible implementation of many of the Jakarta EE 8 specifications we are required to publish our TCK results publically in the format below. So where do we want
 to do this.
 
Some options;
 
By attaching TCK results to the release tag on Github?
By using the wiki on Github to add the results?
By using the website to host the results?
 
This will become a pressure point soon when people demand we host their spec TCK results.
 
Steve
 
From: Steve Millidge (Payara)
Sent: 26 July 2019 15:44
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: Hosting TCK results
 
 
 
 
Hi All,
 
Couple of questions.
 
As part of the requirements to be a compatible implementation of Jakarta EE 8 we have to provide the following info publically.
 
.  The compatible implementation needs to post *their* TCK results summary.  The TCK Process document says the TCK results are not just the finished list of tests, but also:
 
 - Product Name, Version and download URL (if applicable)
 - Implementation runtime Version(s) tested
 - Java runtime used to run the implementation
 - Summary of the information for the certification environment, operating system, cloud, ...
 
 - Statement of Acceptance of the terms of the EFTL
 - Specification Name, Version and download URL
 - TCK Version, digital SHA-256l fingerprint and download URL
 - A statement attesting that all TCK requirements have been met, including any compatibility rules
 
First question.
 
Where would we host this information.
 
Second question, GlassFish is also the compatible implementation of a number of other individual specifications including the Jakarta Connectors, Jakarta Concurrency and others. Should we as a team also host the TCK results for each of
 these specifications and if so where?
 
Steve