Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77475
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.177 as permitted sender)
MIME-Version: 1.0
Sender: rdlowrey@gmail.com
Date: Mon, 22 Sep 2014 12:11:50 -0400
Message-ID: <CAH8Mpn=Zj4ULumj+5r3LKNwuBHP1BSL+V=Q_uXvqPXOUVJjkQA@mail.gmail.com>
To: julien pauli <jpauli@php.net>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec51d218c5be4fb0503a9b5e1
Subject: Re: Re: OpenSSL bug in 5.4.33 and 5.5.17
From: rdlowrey@php.net (Daniel Lowrey)

--bcaec51d218c5be4fb0503a9b5e1
Content-Type: text/plain; charset=UTF-8

> Hi,
>
> That's a bad thing we need to fix ASAP.
>
> I think for 5.6.1 we'll revert it , if not, we'll need an RC2, which
> is something we usually don't do (but as this could involve security,
> we may do it).
> The fix can be merged to 5.5.18RC1, next week, to have an RC cycle if
> not part of a 5.6.1RC2 (tag is tomorrow)
>
> 5.6 and 5.5 actually overlap in the release weeks. 5.6 is planned on
> odd weeks whereas 5.5 is on even weeks.
>
> Waiting for Ferenc's advice anyway.
>
> Julien.P

I have no issues with reverting at this point as that's the best route to
get stable releases back on track. I thought I had fixed some really old
bugs with those commits but the medicine turned out to be worse than the
disease. My apologies again for letting those problems sneak into releases
:/

--bcaec51d218c5be4fb0503a9b5e1--