Introduce semantic versioning for APIB #14
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
| ## Backwards Compatibility | ||
|
|
||
| This is entirely backwards compatible, since the previous released versions are | ||
| the same and this only affects upcoming versions. |
There was a problem hiding this comment.
previous released versions are the same
What do you mean by this sentence?
|
I am okay with this, but I wonder about backward compatibility. Also, there are a few things that need to be finalised. Like:
This sounds like a good idea, but "if it ain't broke don't fix 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.
This RFC proposes that the API Blueprint language and specification are versioned via Semantic Versioning, and there is a CHANGELOG file including a list of changes for each release.