On Fri, Sep 22, 2017 at 1:25 PM, Jim Jagielski <[email protected]> wrote: > We can wait. No reason to rush if we can hold off for a bit > and ensure that 2.4.28 is as ready to go as possible.
Since the C-L issue is not a (recent) regression, I would just as well bank the aging CVE fix now with a release rather than waiting for a potentially destabilizing change.
