[openstack-dev] [stable] New config options, no default change

Ihar Hrachyshka ihrachys at redhat.com
Tue Nov 25 14:10:08 UTC 2014

Hash: SHA512

On 16/11/14 20:17, Jay S. Bryant wrote:
> All,
> This is a question I have been struggling with for Cinder recently.
> Where do we draw the line on backports.  How do we handle config changes?
> One thing for Cinder I am also considering, in addition to whether it
> changes the default functionality, is whether it is specific to the
> submitter's driver.  If it is only going to affect the driver I am more
> likely to consider it than something that is going to impact all of Cinder.
> What is the text that should be included in the commit messages to make
> sure that it is picked up for release notes?  I want to make sure that
> people use that.

I'm not sure anyone tracks commit messages to create release notes. A
better way to handle this is to create a draft, post it in review
comments, and copy to release notes draft right before/after pushing the
patch into gate.

> Thanks!
> Jay
> On 11/11/2014 06:50 AM, Alan Pevec wrote:
>>> New config options may not change behavior (if default value preserves
>>> behavior), they still make documentation more incomplete (doc, books,
>>> and/or blogposts about Juno won't mention that option).
>> That's why we definitely need such changes described clearly in stable
>> release notes.
>> I also lean to accept this as an exception for stable/juno, I'll
>> request relnote text in the review.
>> Cheers,
>> Alan
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)


More information about the OpenStack-dev mailing list