Robert Collins wrote: > On 13 April 2015 at 22:04, Thierry Carrez <thie...@openstack.org> wrote: >> How does this proposal affect stable branches ? In order to keep the >> breakage there under control, we now have stable branches for all the >> OpenStack libraries and cap accordingly[1]. We planned to cap all other >> libraries to "the version that was there when the stable branch was >> cut". Where would we do those cappings in the new world order ? In >> install_requires ? Or should we not do that anymore ? >> >> [1] >> http://specs.openstack.org/openstack/openstack-specs/specs/library-stable-branches.html > > I don't think there's a hard and fast answer here. Whats proposed > there should work fine. > [...] > > tl;dr - I dunno :)
This is not our first iteration at this, and it feels like we never come up with a solution that covers all the bases. Past failure can generally be traced back to the absence of the owner of a critical puzzle piece... so what is the way forward ? Should we write a openstack-specs and pray that all the puzzle piece owners review it ? Should we lock up all the puzzle piece owners in the QA/Infra/RelMgt Friday sprint room in Vancouver and get them (us) to sort it out ? -- Thierry Carrez (ttx) __________________________________________________________________________ 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
