API Versioning Strategy

Our API versioning strategy is described here.

The major version will change on incompatible API changes. Each major version has its own base path. Client applications will need to be changed.

The minor version will change when backward compatibile functionality is introduced to the Ocelot API. Examples are backward compatibile functionality are: a new functional area, and purely-additive changes to an existing functional area. Client applications will not need to be changed if there is no desire to use the introduced functionliaty.

The patch version will change when backward compatible bug fixes are deployed at the Ocelot API. Client applications will not need to be changed for these bug fixes.