[openstack-dev] [all][pbr] splitting our deployment vs install dependencies
joe.gordon0 at gmail.com
Tue Apr 14 21:33:40 UTC 2015
On Tue, Apr 14, 2015 at 2:36 AM, Thierry Carrez <thierry at openstack.org>
> Robert Collins wrote:
> > On 13 April 2015 at 22:04, Thierry Carrez <thierry at 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. 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 ?
> >> 
> > I don't think there's a hard and fast answer here. Whats proposed
> > there should work fine.
> > [...]
> > tl;dr - I dunno :)
This is the part of the puzzle I am the most interested in. Making sure
stable branches don't break out from underneath us forcing us to go into
fire fighting mode.
> 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 ?
++, we really need to get this sorted out.
> Thierry Carrez (ttx)
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev