On Mon, Jun 29 2015, Ildikó Váncsa wrote:

> I think removing options from the API requires version bump. So if we plan to
> do this, that should be introduced in v3 as opposed to v2, which should remain
> the same and maintained for two cycles (assuming that we still have this 
> policy
> in OpenStack). It this is achievable by removing the old code and relying on
> the new repo that would be the best, if not then we need to figure out how to
> freeze the old code.

This is not an API change as we're not modifying anything in the API.
It's just the endpoint *potentially* split in two. But you can also
merge them as they are 2 separate entities (/v2/alarms and /v2/*).
So there's no need for a v3 here.

As the consensus goes toward removal, I'll work on a patch for that.

-- 
Julien Danjou
/* Free Software hacker
   http://julien.danjou.info */

Attachment: signature.asc
Description: PGP signature

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to