The Technology Compatibility Kit (TCK) should be updated more carefully than the RI, since we want to avoid the situation where a change breaks an implementation that had been running successfully (passing all tests) against a previous version of the TCK.This might apply even if the fix is a "bug" in that the test logic clearly contradicts the intentions and behaviors stated in the specification. On the other hand changes like improving diagnostics and making the TCK more configurable and user-friendly should be able to be made without this type of concern. We intend to make changes on a case-by-case basis, and deal with the above risk by:
The TCK isn't primarily delivered via Maven but rather via the download zip. The Maven version is included for identifying correspondences to other updates, and does not imply you should pick up the TCK from Maven (although some artifacts are indeed delivered to Maven).
We updated the SigTest signature files
This was the first delivery marked "Final Release".