Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

With my operator hat on I think the release notes are the right place for these changes. Belmiro On Wed, Nov 18, 2015 at 4:58 PM, Alexis Lee wrote: > Sylvain Bauza said on Wed, Nov 18, 2015 at 04:48:50PM +0100: > > >This is just for the case of "we're going to change the default

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Sylvain Bauza said on Wed, Nov 18, 2015 at 04:48:50PM +0100: > >This is just for the case of "we're going to change the default on the > >next release". I think in that case, a release note is the right thing. > >We don't need new fancy code for that. > > I usually hate saying just +1 in an

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

On 11/17/2015 05:31 PM, Matt Riedemann wrote: > > > On 11/17/2015 2:05 PM, Sylvain Bauza wrote: >> >> >> Le 17/11/2015 20:25, Sean Dague a écrit : >>> On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: > Often in Nova we introduce an option

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Le 18/11/2015 16:34, Sean Dague a écrit : On 11/17/2015 05:31 PM, Matt Riedemann wrote: On 11/17/2015 2:05 PM, Sylvain Bauza wrote: Le 17/11/2015 20:25, Sean Dague a écrit : On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: Often in Nova we

[openstack-dev] [oslo] [nova] default-next-release opt flag

Often in Nova we introduce an option defaulted off (so as not to break people) but then we want to make it default in the next release. Someone suggested an opt flag to mark this but I don't know what impact they wanted it to have. IE how the user should be alerted about the presence of these

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Excerpts from Alexis Lee's message of 2015-11-17 09:28:31 -0800: > Often in Nova we introduce an option defaulted off (so as not to break > people) but then we want to make it default in the next release. > > Someone suggested an opt flag to mark this but I don't know what impact > they wanted it

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

On 11/17/2015 01:48 PM, Matt Riedemann wrote: > > > On 11/17/2015 11:28 AM, Alexis Lee wrote: >> Often in Nova we introduce an option defaulted off (so as not to break >> people) but then we want to make it default in the next release. >> >> Someone suggested an opt flag to mark this but I don't

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Le 17/11/2015 20:25, Sean Dague a écrit : On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: Often in Nova we introduce an option defaulted off (so as not to break people) but then we want to make it default in the next release. Someone suggested an opt

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

On 11/17/2015 2:05 PM, Sylvain Bauza wrote: Le 17/11/2015 20:25, Sean Dague a écrit : On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: Often in Nova we introduce an option defaulted off (so as not to break people) but then we want to make it default