[openstack-dev] [stable] New config options, no default change
Jay S. Bryant
jsbryant at electronicjungle.net
Sun Nov 16 19:17:47 UTC 2014
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.
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.
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev