Update Status, Timeline, Next Steps #41
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update README: - Provide separate status of CCF specs and CCF codec. - Update Timeline to include milestones reached on Dec 9 and Dec 15. - Add note about more tests being required even though CCF codec passed all ported tests from JSON-Cadence Data Interchange Format. - Add note about CCF codec eventually needing fuzz testing by the Cadence team before being used in production.
fxamacker
changed the title
Remove sentence mentioning EN and nodes because CCF or CBOR security considerations can be described without it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update README: