[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jakarta.ee-spec] Adding or fixing tests in a TCK's service release
|
Another aspect to capturing from today's spec committee call.
We are fixing TCK tests to ensure they run on Java 11. Strictly speaking this is not allowed per the Jakarta EE TCK Process 1.0 [1]:
How Tests May be Added to a TCK
The only time tests may be added to a TCK are in a major or minor
release. A service release which updates the exclude list MUST not
have test additions or changes.
What this means to communicate is the only action that can be taken is to remove/exclude tests. I argued for being able to fix TCKs, but we decided against it and I was ultimately ok with that as I was confident it would only be a matter of time before we'd want to do it and see the value. Since we are doing it now at large scale for Java 11, we may want to revisit the discussion and policy.
I can see the clear argument that if a spec team wishes to add new tests that would require at least a minor version, but fixing them is ok. If we require a CCR for service releases of TCKs that feels like a less risky thing to do in practice. Our practice now is that we are doing it and we were not planning to create CCRs.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
[1] https://jakarta.ee/committees/specification/tckprocess/
