-
Notifications
You must be signed in to change notification settings - Fork 534
Temporarily Remove TCK Implementation #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
+1 |
+1 Before bringing it back we need to have at least two reference implementations of the new semantics so that we know that the TCK verifies the right thing. |
+1 |
Based on agreement above I have submitted and will now merge a pull request to remove the TCK implementation but leave the folder structure in place. |
Will try to be candidate to the reference implementation :) |
removing it makes sense for now, +1 @benjchristensen :) |
I propose temporarily removing the TCK implementation and that we stop working on it until we arrive at a fairly stable agreement on the API and contract.
There is significant discussion going on in #19 and #37 that is changing the contract, and I expect further changes beyond these. The TCK impedes rapid iteration and confuses things until the contract is clearly defined.
Do we have agreement to delete what's currently there (and about to be obsolete) until we reach an agreement on contract?
The text was updated successfully, but these errors were encountered: