Make spec versioning explicit #307
Open
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
The relationship of the old and new specs was not entirely clear, and the spec versions did not have names to refer to them by; implementors can now indicate which version they support, if needed. This commit establishes the year of release as the version name, makes it clear that the 2013 version is the current and stable one, and hints that support for the 2011 version is not necessary in new implementations. (Also includes some minor language clarifications.)
Contributor
Author
|
@frsyuki Would it be possible to get some feedback on this PR? I think making this clarification would be very helpful to others considering using this format. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The relationship of the old and new specs was not entirely clear, and the
spec versions did not have names to refer to them by; implementors can now
indicate which version they support, if needed.
This commit establishes the year of release as the version name, makes
it clear that the 2013 version is the current and stable one, and hints
that support for the 2011 version is not necessary in new implementations.
(Also includes some minor language clarifications.)