Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> ---------- 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?

I think it's ok to introduce new config options that do not change
default behaviour for major and critical issues. Quoting rules, only
'*Incompatible* config file changes' are forbidden.

Note that we may even change default behaviour if it exposes users to
major security threats. Though the backport is SecurityImpact, it's
not CVE, so usual considerations should be applied (whether the patch
is self-contained, risk of regression...)

I think the fix is good to go.

> 
> Thanks
> 
> [0] https://review.openstack.org/#/c/131987/
> 
> -- Kind Regards, Dave Walker
> 
> _______________________________________________ OpenStack-dev
> mailing list OpenStack-dev at lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iQEcBAEBCgAGBQJUYeOGAAoJEC5aWaUY1u57NW4H+QHdKaIaOnwGpaaV6d1hpvwp
6MCfndWrKsTq+xSQr184JiZHLLskHJ7Hp5426B5n52q80rz4VvnVixU/oSg7ivBe
UV5S+i7y7IBDqlGXRYHaKa9EeDqih5YK4W6RQEWZNuWsZoQALVOON2DYflnqSOJA
BgBZy9jnKyE7kqpbApHddsNLZR2SVcOMkUVBNoHM9hgmSnDigvWFSsHq7jfW88Tt
8IP9s/vPv1hReis88oRcJEgwzWYts8FoC3vFAK04VYxRNRitrQs2O3RMKgDP8TTj
z1DabUapPkc8DzK8McEp46RmHO2VipCL/ErIS9p6UH8HDBdYmX5BrsJF3ziUBAc=
=vqQ+
-----END PGP SIGNATURE-----