Alibaba Dragonwell JDK TCK/JCK Compliance

[modernDayPablum]

>From a recent internet discussion [1] I've been given reason to think
that at least
one of Alibaba's Dragonwell [2] JDKs (8 or 11) is not in compliance with
the TCK/JCK.

Please can anybody in the list offer answers to the following questions:

1. Is the OCTLA Signatories List [3] up-to-date?

2. Is the Alibaba Dragonwell JDK 8 TCK/JCK compliant?

3. Is the Alibaba Dragonwell JDK 11 TCK/JCK compliant?

4. Where can I read about any official governance on what claims OpenJDK
vendors are
   allowed or expected to make about their TCK compliance?

5. What is the OpenJDK project lead's position on vendors representing
that they are
   TCK compliant, if it is the case that the vendor is not actually TCK
compliant?

6. What are the risks (if any) to end users developing and running
software on an
   OpenJDK implementation that is not TCK compliant?

7. As an application developer implementing/deploying software built with an
   OpenJDK implementation, how can I know with 100% certainty that a
vendor's
   claims of TCK/JCK compliance is true?

8. Is my assumption correct that Alibaba is a signatory to only OpenJDK
Community TCK
   and EA TCK License Agreement V 2.0 [4] but is not currently a
signatory to OpenJDK
   Community TCK and EA TCK License Agreement V 3.0? [5]

Thanks in advance.

----

[1] https://bit.ly/pron98Ali
[2] https://bit.ly/aliDragon
[3] https://bit.ly/OCTLASigs
[4] https://bit.ly/octlaJDK8
[5] https://bit.ly/octlaJDK9