On 01/15/2015 08:38 AM, Thierry Carrez wrote: > Sean Dague wrote: >> The policy decision to cap stable requirements was agreed to previously >> (and at summit this year), it just needs someone to implement. > > +1 > > We started to implement it (in Oslo libraries iirc) and then reverted > because we encountered problems. We concluded a proper cross-project > spec should be written so that we can try to anticipate issues better. > > I don't have a totally clear view of the issue(s) we encoutered last > time, though. Could someone write a postmortem or point me to one ? Or > was the upgrading components issue (fixed in > https://review.openstack.org/#/c/142075/) the only problem ?
My recollection is the component upgrade order was a big problem, but not the only one. The other thing that happened was partial capping doesn't work, because something else moves forward and breaks you from below. So the patch will need to hit everything at once. Unresolved entirely is the tertiary dependencies (not direct dependencies of any OpenStack project). That will need another mechanism to seed them before any installation happens. Whether or not pip should be pinned is also a good question, especially because pbr requires pip, so the install -U on pbr tends to uplift pip even if it was previously downgraded. That's the things I can think off from the top of my head. -Sean -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev