[openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

Ihar Hrachyshka ihrachys at redhat.com
Wed Aug 10 09:04:48 UTC 2016

Duncan Thomas <duncan.thomas at gmail.com> wrote:

> So I tried to get into helping with the cinder stable tree for a while,  
> and while I wasn't very successful (lack of time and an inability to  
> convince my employer it should be a priority), one thing I did notice it  
> that much of the breakage seemed to come from outside cinder - many of  
> the libraries we depend on make backwards incompatible changes by  
> accident, for example. Would it be possible to have a long-term-support  
> branch where we pinned the max version of everything for the gate, pips  
> and devtstack? I'd have thought (and I'm very willing to be corrected)  
> that would make the stable gate, well, stable, such that it required far  
> less work to keep it able to run a basic devstack test plus unit tests.

The solution for that is in place: upper-constraints.txt, they are not  
bumped with no particular reason in stable/* branches. So just make sure  
that your project uses those for gating, and you should be safe from 99% of  
breakages. Neutron successfully uses the system for all stable branches,  
and believe me, it’s makes a huge difference.


More information about the OpenStack-dev mailing list