api-blueprint-rfcs
api-blueprint-rfcs copied to clipboard
Introduce semantic versioning for APIB
trafficstars
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.
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"