Open Stack

Michael Still <mikal at stillhq.com> writes:

> 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.

Excellent idea.  I just wrote a change to Zuul that will let us run a
job iff a change is made to specific files.  We'll use that to have a
job that checks that a proposed dependency update is permitted by the
current state of the requirements repo, and if not, output a useful
failure message.

Thanks!

-Jim