[openstack-dev] New process for updating requirements

Michael Still mikal at stillhq.com
Wed Mar 6 12:56:41 UTC 2013


On Tue, Mar 5, 2013 at 10:40 PM, James E. Blair <jeblair at openstack.org> wrote:
> Hi,
>
> In order to update a requirement for an OpenStack project, you will
> first need to propose the new version to the openstack/requirements
> project.  Once it is merged there, it will appear in the OpenStack pypi
> mirror, and only then can it be used in an OpenStack project.  This is
> the first stage in a process to centralize and improve dependency
> management discussed at the grizzly summit.

I like this, but I wonder if we should have a jenkins check that let's
people know that they've updated requirements but forgotten this step?
I worry about new person confusion.

Michael



More information about the OpenStack-dev mailing list