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

Ben Swartzlander ben at swartzlander.org
Tue Aug 9 23:46:48 UTC 2016

On 08/09/2016 06:56 PM, Mike Perez wrote:
> On 10:31 Aug 06, Sean McGinnis wrote:
> <snip>
>> I'm open and welcome to any feedback on this. Unless there are any major
>> concerns raised, I will at least instruct any Cinder stable cores to
>> start allowing these bugfix patches through past the security only
>> phase.
> As others have said and as being a Cinder stable core myself, the status-quo
> and this proposal itself are terrible practices because there is no testing
> behind it, thereby it not being up to the community QA standards set. I will be
> issuing -2 on these changes in the stable branch regardless of your
> instructions until the policy has changed.

I agree we can't drop the testing standards on the "stable" branches. 
I'm not in favor of that. I'd rather use differently-named branches with 
different and well-documented policies. Ideally the branches would be 
named something like driver-fixes/newton and driver-fixes/ocata, etc, to 
avoid confusion with the stable branches.

-Ben Swartzlander

> If you want to change that, work with the stable team on the various options
> provided. This tangent of people whining on the mailing list and in
> #openstack-cinder is not going to accomplish anything.

More information about the OpenStack-dev mailing list