Skip to content
This repository was archived by the owner on Nov 8, 2024. It is now read-only.

Comments

Introduce semantic versioning for APIB#14

Open
kylef wants to merge 1 commit intomasterfrom
kylef/semver
Open

Introduce semantic versioning for APIB#14
kylef wants to merge 1 commit intomasterfrom
kylef/semver

Conversation

@kylef
Copy link
Member

@kylef kylef commented Feb 9, 2016

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.

## Backwards Compatibility

This is entirely backwards compatible, since the previous released versions are
the same and this only affects upcoming versions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

previous released versions are the same

What do you mean by this sentence?

@pksunkara
Copy link
Contributor

I am okay with this, but I wonder about backward compatibility. Also, there are a few things that need to be finalised. Like:

  • Will we support multiple versions of APIB? Or is it always going to be the latest version?
  • APIB is pretty stable, so I don't know if we really need the major and minor numbers from semantic versioning.

This sounds like a good idea, but "if it ain't broke don't fix it"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants