Open Stack

Excerpts from Robert Collins's message of 2015-07-14 09:05:43 +1200:
> On 14 July 2015 at 02:10, Jeremy Stanley <fungi at yuggoth.org> wrote:
> > On 2015-07-13 09:39:36 -0400 (-0400), Doug Hellmann wrote:
> > [...]
> >> On the other hand, how much longer will we be supporting Juno? A
> >> matter of months, right?
> >
> > The reason it's being brought up again at this point is to ask
> > whether it's more important that we keep master clients/libs working
> > with 2.6 for several more months, or be able to push forward with
> > our constraints overhaul between now and then. I'll be hard to have
> > the necessary tooling in place before the liberty release if we
> > can't actually use it before then (since that's roughly when juno
> > EOL is scheduled).
> 
> Additional detail:
>  - generating 2.6 pins for global requirements requires access to 2.6
> where the periodic job runs *and where devs are generating updates*.
>  - so that means docker or lxc or something in both the CI system and
> widely available for devs.
> 
> So its a non-trivial impact; we can do it to move things forward, but
> it would be a lot cheaper not to.

I don't *want* to keep 2.6 support around, and I do understand that
the requirements work will be made easier.  I'm just trying to
understand what other impact dropping it will have.

Doug