[openstack-dev] How to stage client major releases in Gerrit?

Robert Collins robertc at robertcollins.net
Thu Nov 21 18:39:45 UTC 2013

On 22 November 2013 02:57, Monty Taylor <mordred at inaugust.com> wrote:

> This is a really complex one because of the gate. It's not just about
> the semver major version bump. I agree with earlier sentiment - the way
> to handle breaking changes is to bump the major version, and on the
> surface I don't have a problem with us doing that, since there is
> already a mechanism to deal with that.
> HOWEVER - it's more complex than that with us, because the client libs
> are part of our integration.
> We've already agreed on and have been operating on the assumption that
> client libs do not break rest api backwards compat. We're 3 seconds away
> from landing gating tests to ensure this is the case. The reasoning here
> is that an end user of OpenStack should not need to know what version of
> OpenStack a vendor is running - the latest python-glanceclient should
> work with diablo and it should work with icehouse. Nothing in this
> thread breaks that - I just bring it up because it's one of the overall
> design points that we'll be rubbing against.

I don't understand why branches would be needed here *if* the breaking
changes don't impact any supported release of OpenStack.


Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud

More information about the OpenStack-dev mailing list