In Nova we have done the following: - add a warning in the current version that this will be deprecated in K - start of K drop the code It is also important to have an upgrade path. What happens if I have my RYU plugin in production and I upgrade to the next version. That should be clearly documented. I think that maybe we should consider on working on a migration scheme - from plugin A to plugin B. Thanks Gary
On 7/30/14, 8:17 PM, "YAMAMOTO Takashi" <yamam...@valinux.co.jp> wrote: >hi, > >what's the right procedure to deprecate a plugin? we (ryu team) are >considering deprecating ryu plugin, in favor of ofagent. probably in >K-timeframe, if it's acceptable. > >YAMAMOTO Takashi > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
