| [jakarta.ee-spec.committee] Certification Requests for Specifications with no TCK |
We appear to have been inconsistently handling now we're supposed to handle certification for Specifications with no TCK. Kevin filed for both the Spec and Platform: - https://github.com/jakartaee/specifications/pull/75 - https://github.com/jakartaee/specifications/pull/19 Arjan did it only for the Spec and not the Platform: - https://github.com/jakartaee/specifications/pull/52 I did it only for the Platform and not the Spec: - https://github.com/jakartaee/specifications/pull/91 - https://github.com/jakartaee/specifications/pull/36 We should discuss this Wednesday. Open questions using Interceptor as an example: - Is the Interceptor spec project, for example, supposed to evaluate all the CTS results or just the interceptor tests? - If the full results, is the Interceptor project supposed now completely understand full CTS certification requirements? - Can you call yourself Interceptor-certified if you pass just the Interceptor tests? - What would it mean if say the Interceptor project rejected the full CTS certification but the Platform accepted the same results? - What is the value this brings for the overhead it creates? For Managed Beans it is particularly odd as we're filling the same request twice in the same project to be evaluated by the same people. -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com