Open Stack

On 02/12/13 09:06 -0500, Russell Bryant wrote:
>On 12/02/2013 08:53 AM, Doug Hellmann wrote:
>So, to clarify, possible flows would be:
>
>1) An API moving to a library as-is, like rootwrap
>
>   Status: Maintained
>   -> Status: Graduating (short term)
>   -> Code removed from oslo-incubator once library is released

We should make the module print a deprecation warning which would be
more like a 'transition' warning. So that people know the module is
being moved to it's own package.

>
>2) An API being replaced with a better one, like rpc being replaced by
>oslo.messaging
>
>   Status: Maintained
>   -> Status: Obsolete (once an RC of a replacement lib has been released)
>   -> Code removed from oslo-incubator once all integrated projects have
>been migrated off of the obsolete code

We've a deprecated package in oslo-incubator. It may complicate things
a bit but, moving obsolete packages there may make sense. I'd also
update the module - or package - and make it print a deprecation
warning.

FF

-- 
@flaper87
Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131202/21830dba/attachment.pgp>