Open Stack

As I understand it, such a patch wouldn't pass gating as the dependency
wouldn't be available on our pypi mirror.


-Dolph


On Wed, Mar 6, 2013 at 6:56 AM, Michael Still <mikal at stillhq.com> wrote:

> 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
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130306/62bd021d/attachment.html>