[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Core-updates timeline
From: |
Leo Famulari |
Subject: |
Re: Core-updates timeline |
Date: |
Sun, 2 Oct 2016 14:50:34 -0400 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
On Sun, Oct 02, 2016 at 03:38:58PM +0200, Ludovic Courtès wrote:
> Hi!
>
> Leo Famulari <address@hidden> skribis:
>
> > On Sat, Oct 01, 2016 at 03:22:36PM +0200, Ludovic Courtès wrote:
> >> I pushed simplified versions of these two patches as
> >> 56ee1d2015e9b2c55d34f19c70b06eefe8a20c76 and
> >> 156c0810e936413ac554e2883343b3b40695cfdc.
> >>
> >> I think this was the last non-bug-fix change for this core-updates
> >> cycle. :-)
> >
> > Cool :)
> >
> > I've been waiting for libarchive 3.2.2 [0] so that I can graft it on
> > master and ungraft it on core-updates. But, I can try cherry-picking the
> > most important changes today. When do you hope to freeze core-updates?
> > Do you want me to try cherry-picking?
>
> There’s was another Bash-related issue that I just fixed, and Hydra is
> now rebuilding the “core” package subset. If everything is fine when
> it’s done, which could be tomorrow, we could freeze.
>
> We could wait an additional day for libarchive if it’s more convenient,
> but maybe not longer than that.
>
> What do you think would be the most convenient approach?
I will send a patch that cherry-picks what I think are the most
important bug fixes. I can't guess when libarchive 3.2.2 will be
released.