[openstack-dev] [sahara] summit wrap-up: backward compat

Matthew Farrellee matt at redhat.com
Wed May 28 19:55:23 UTC 2014


On 05/28/2014 03:50 PM, Andrew Lazarev wrote:
>
>     for juno we should just have a v1 api (there can still be a v1.1
>     endpoint, but it should be deprecated), and maybe a v2 api
>
>     +1 any semantic changes require new major version number
>
>     +1 api should only have a major number (no 1.1 or 2.1)
>
>
> In this case we will end up with new major number each release. Even if
> no major changes were done.

a semantic addition (e.g. adding EDP and v1.1) doesn't warrant a new 
version.

so more specifically: +1 any change in existing semantics requires a new 
major version number

but maybe i'm missing why we'd end up w/ a new version per release

best,


matt




More information about the OpenStack-dev mailing list