On Thu, Jan 14, 2016 at 11:58 AM, Jay Pipes <[email protected]> wrote: > On 01/14/2016 11:45 AM, Ronald Bradford wrote: >> >> Presently the oslo.config Opt class has the attributes >> deprecated_for_removal and deprecated_reason [1] >> >> I would like to propose that we use deprecated_reason (at a minimum) to >> detail in what release an option was deprecated in, and what release it >> is then removed in. > > > You mean what release it *will* be removed in, right? Clearly, once it's > removed, there won't be any indication it ever existed ;) >
Yes, in what release it is to be removed, e.g. Mitaka. So when is that release cycle, i.e. now once removed there is no record. > > Any improvement in this regard I think would enhance the user experience > considerably, thank you Ronald for tackling this area. I'd also suggest > cc'ing (or sending a separate ML post) to the openstack-operators@ ML to > gather feedback from ops folks. > will do! __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
