Open Stack

Excerpts from Robert Collins's message of 2015-04-25 07:21:18 +1200:
> I think it needs a three-step dance.
> 
> 1) Commit the intent to deprecate but don't signal it programmatically.

I'm not sure what this means. A spec? A bug? A comment?

> 2) Work with known direct users to remove usage.
> 3) Programmatically signal deprecation and maintain until a major
> release is made.
> 
> -Rob
> 
> On 25 April 2015 at 07:06, Julien Danjou <julien at danjou.info> wrote:
> > Hi Oslo team!
> >
> > So what's your deprecation path?
> >
> > I sent a patch for oslo.utils¹ using debtcollector, our new fancy
> > deprecation tool, and I got a -2 stating that there's no way we
> > deprecate something being used, and that we need to remove usage from
> > the projects first.
> >
> > I don't necessarily agree with this, but I accepted the challenge
> > anyway. I started by writing only patches for Nova² and Cinder³, and now I
> > see people complaining that my patch can't be merged because the
> > function is not deprecated in Oslo.
> >
> > So before I start flipping tables, what do we do?
> >
> >
> > ¹  https://review.openstack.org/#/c/148500/
> >
> > ²  https://review.openstack.org/#/c/164753/
> >
> > ³  https://review.openstack.org/#/c/165798/
> >
> > --
> > Julien Danjou
> > -- Free Software hacker
> > -- http://julien.danjou.info
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>