Open dblevins opened 3 years ago
Should I fork the https://github.com/jakartaee/jakarta.ee repo and create a pr for https://github.com/jakartaee/jakarta.ee/tree/src/content/committees/specification/tckprocess?
The TCK Process document should be updated with:
* Recommendation that exclude lists should be zeroed for a major version
This may hit some schedule contention if implementations discover late that their previously challenged but not yet fixed tests are causing test failures which could (possibly) mean fewer compatible implementations in the major version release (which can cause other problems). I'm just mentioning here for future discussion possibly when reviewing the tck process changes.
* Process for releasing a point revision of a TCK
The agreed process for releasing a point revision of a TCK entails filing an issue in the https://github.com/jakartaee/specifications repository with the following details:
* Link to the TCK release to be published * Updated TCK links in the specification's `_index.md` file * A high-level description of what tests were excluded from the TCK and why
+1
Question: do we want any particular label on these types of issues?
Yes, challenge
is already required by the 1.0 TCK process doc, IMO we should continue to use that.
Cesar to check w/ David to determine if this issue can be closed, it appears that the items rasied in the issue have been resolved.
The TCK Process document should be updated with:
The agreed process for releasing a point revision of a TCK entails filing an issue in the https://github.com/jakartaee/specifications repository with the following details:
_index.md
fileQuestion: do we want any particular label on these types of issues?