Open Stack

Hi Dave,

I'm forwarding your message to openstack-stable-maint, that list has
been made read-only as decided on release management meetup on Friday
Nov 7 2014, see under "* Stable branches" in
https://etherpad.openstack.org/p/kilo-infrastructure-summit-topics
I have set explicit Reply-To: header to
openstack-dev at lists.openstack.org in list options but it doesn't seem
to work, I'll investigate that.

All stable maintenance related discussion should happen on
openstack-dev with [stable] tag in the subject.

Cheers,
Alan

---------- Forwarded message ----------
From: Dave Walker <email at daviey.com>
To: openstack-stable-maint <openstack-stable-maint at lists.openstack.org>
Date: Mon, 10 Nov 2014 21:52:23 +0000
Subject: New config options, no default change

Hi,

Looking at a stable/juno cinder proposed change[0], I came across one
that introduces a new config option.

The default is a noop change for the behaviour, so no bad surprises on upgrade.

These sort of changes feel like they are outside the 'no config
changes' rule, but we have not really discussed this.

What do others think?

Thanks

[0] https://review.openstack.org/#/c/131987/

--
Kind Regards,
Dave Walker