[jakarta.ee-spec.committee] TCK Issues to Resolve

[Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx>]

The Draft of the TCK document (see link below) has been available and commented on.  More comments are welcome.

https://docs.google.com/document/d/1civpv_KLHvUXgILQYCh0HR9Xgsv78PISPc9wbRUUKMc/edit?usp=sharing

While some issues are easy to resolve in comments on the document others require a more focused resolution. These other issues are enumerated below.  Please take the time to read and respond.

1. TCK Challenges: When a vendor challenges a TCK test who should determine if the challenge is valid?   The following options have been suggested:
   
• The TCK Project (assuming its separate from the Specification Project)
• The Specification Project with Escalation to the Specification Committee allowed
• The Specification Committee only.
2. Vendor Releases and TCK patches:  If a vendor releases a new version minor of their product, which continues to support the same specifications claimed by the original major version, can the new minor version be tested against the original TCK used for the original version, or does it need to be tested against the latest patch/revision of that TCK?
3. Versioning:  Should the TCK versions match the major and minor versions of the Specification?
4. Versioning:  If an errata level error (anything that doesn't change the described behavior of the software or its API usage) is found in a specification which of the following options should we use?
• An errata is published with the correction but the specification is not updated.
• The specification is updated and a new Rev version is released. (e.g. X Specification Version 1.2 Rev 2)
• The specification is updated and a new Maintenance version is released (e.g. X Specification Version 1.2 MR 2)
5. Specification Updates and TCK updates:  What kinds of corrections to a specification should require a new version of the TCK?

thanks,

Richard