Re: [openstack-dev] [ironic][openstackclient] deprecation process

2016-05-16 Thread Loo, Ruby
v@lists.openstack.org>> Date: Thursday, May 12, 2016 at 12:05 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [ironic][openstackclient] deprecati

Re: [openstack-dev] [ironic][openstackclient] deprecation process

2016-05-12 Thread Steve Martinelli
I thought we had this written down somewhere but I can't find it. The OSC deprecation process is two major releases. So if something was deprecated in L, it is removed in N. This goes for optional parameters being renamed / dropped, or commands being dropped / renamed. If an optional parameter is

[openstack-dev] [ironic][openstackclient] deprecation process

2016-05-12 Thread Loo, Ruby
Hi OpenStackClient folks, Ironic is following the standard deprecation process [1]. We added an OSC plugin and realized that we didn’t get the commands quite right. This patch [2] adds the right commands and deprecates the wrong ones. My question is what the deprecation process might be. Since