Revert "Clarify backwards compatibility for major version 0" #488
Conversation
This file contains 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
This reverts commit 0f25f18, opencontainers#253. Now that we're on to 1.0, we don't need to talk about 0.x. And the lack of 0.x backwards compatability is covered by SemVer 2.0 section 4 [1]: Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable. so removing the echo from our spec doesn't actually change anything. The conflict is due to 4e63ee0 (config: qualify the name of the version field, 2016-01-13, opencontainers#309), and only impacted the context and line-wrapping around the sentence I'm removing. Conflicts: config.md [1]: http://semver.org/spec/v2.0.0.html Signed-off-by: W. Trevor King <wking@tremily.us>
|
LGTM |
1 similar comment
|
LGTM |
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.
This reverts commit 0f25f18 (#253). Now that we're on to 1.0, we don't need to talk about 0.x. And the lack of 0.x backwards compatability is covered by SemVer 2.0 section 4:
so removing the echo from our spec doesn't actually change anything.