[openstack-dev] [oslo] maintenance policy for code graduating from the incubator

Sandy Walsh sandy.walsh at RACKSPACE.COM
Fri Nov 29 19:14:30 UTC 2013

So, as I mention in the branch, what about deployments that haven't transitioned to the library but would like to cherry pick this feature? 

"after it starts moving into a library" can leave a very big gap when the functionality isn't available to users.


From: Eric Windisch [eric at cloudscaling.com]
Sent: Friday, November 29, 2013 2:47 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

> Based on that, I would like to say that we do not add new features to
> incubated code after it starts moving into a library, and only provide
> "stable-like" bug fix support until integrated projects are moved over to
> the graduated library (although even that is up for discussion). After all
> integrated projects that use the code are using the library instead of the
> incubator, we can delete the module(s) from the incubator.


Although never formalized, this is how I had expected we would handle
the graduation process. It is also how we have been responding to
patches and blueprints offerings improvements and feature requests for

Eric Windisch

OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

More information about the OpenStack-dev mailing list