Open Stack

On 10/31/2012 12:08 PM, Gary Kotton wrote:
> Hi,
> Whilst back porting patches to the Quantum stable folsom branch I have encountered a very frustrating problem which I think that should be discussed. All of the stable quantum patches approved in the last few hours are failing unit tests. This seems to be due to one of the imported packages being problematic (the hunch at the moment is that this could be sqlalchemy). At the moment this is under investigation. I am wondering if when we create a stable branch, we should specifically set the pip-requires package numbers.
> Any thoughts?
> Thanks
> Gary

This was discussed at the design summit, with notes kept here:
https://etherpad.openstack.org/process-dependency-management

One of the action items from there is:

* freeze 'sane' version (max major version?) range at release time

So by recording the max version in the pip-requires,
it would mean that newer versions wouldn't be pulled
in, in the future, that might break stuff.
Also distros etc. should not be impacted since packages
manage dependencies independently.

There don't seem to be links to videos or slides
up for any of the design sessions yet.

cheers,
Pádraig.