Excerpts from Ronald Bradford's message of 2016-03-03 09:54:16 -0500:
> > > * When an option is changed, or marked as deprecated, during normal
> > reviews
> > > it should then be identified accordingly with these new attributes.
> > > * The "changed" attribute would only be applicable moving
> > * When an option is changed, or marked as deprecated, during normal
> reviews
> > it should then be identified accordingly with these new attributes.
> > * The "changed" attribute would only be applicable moving forward with a
> > developer change in default value, ranges etc (changing help
Excerpts from Ronald Bradford's message of 2016-03-02 13:40:42 -0500:
> After evaluation of oslo-config-generator and one of it's common uses by
> operators in configuration option evaluation with upgrades, I am proposing
> adding some meta data for all configuration options to provide better
>
After evaluation of oslo-config-generator and one of it's common uses by
operators in configuration option evaluation with upgrades, I am proposing
adding some meta data for all configuration options to provide better
applicable documentation as projects continue to evolve.
I can see an easier
