On 15/10/2017 10:34, Guillermo González de Agüero wrote:|
We do test continuously for TCK compliance and for many more
OS/JVM/DB combinations. At a minimum, though, you have to report one
successful combination to claim compliance (for that particular
I think we're all basically saying the same. "No RI" seems
equivalent "at least one, but not limited to, one RI".
Nobody wants a finished spec without a complaint
implementation. The idea of the single RI made sense with a
somewhat private process and closed source RIs where maybe
even some EG members didn't have access to it. But a truly
open process means everyone has the same rights and has access
from minute 1 to everything.
I also expect to see more specifications being co-lead by
multiple vendors, which will presumably like to have each
their own implementation marked as the "Reference"
implementation. The reference implementations for a spec
version could be defined at the beginning and then the spec
would be finished when the RIs are done.
More response inline.
I support your idea of specific versions
being considered the RI, but open TCKs will make
it easy for users to test themselves. Probably
most vendors will even run TCK tests as part of
their CI pipelines, making the RI "upgradeable".
ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit