Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89758
Return-Path: <ircmaxell@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 94203 invoked from network); 8 Dec 2015 16:09:29 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 8 Dec 2015 16:09:29 -0000
Authentication-Results: pb1.pair.com smtp.mail=ircmaxell@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=ircmaxell@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
X-PHP-List-Original-Sender: ircmaxell@gmail.com
X-Host-Fingerprint: 74.125.82.45 mail-wm0-f45.google.com  
Received: from [74.125.82.45] ([74.125.82.45:38062] helo=mail-wm0-f45.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 77/CE-31749-7B007665 for <internals@lists.php.net>; Tue, 08 Dec 2015 11:09:28 -0500
Received: by wmec201 with SMTP id c201so35901370wme.1
        for <internals@lists.php.net>; Tue, 08 Dec 2015 08:09:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        bh=35sR/C0Miu/SqRMOl4Rk20DHZG33bJHU0D7mu/w+R/w=;
        b=OIdwKZAXGqtOIvaEp6hSpBNc0F7MdsGAHK4GfbSO3InA1nTZ3mym4g3s34vxb0NdXY
         5gRQV9MpUXdI6rU0qSuXjIvoH4mPyYPbyIACdkzpxHha4U1jNZrNZkp1CgmVteTsIAe+
         4ec5sEcylWQV/wff5DuUXyGNyAoOeN1rYY7X556bGXEdHeEgNG4Cvy9jXZRWHII2yE5t
         EcgwTJTbaukVPJ4l0O7+fPCIFmNWf3wQhKVwr0SVJnR/a0Cv8QBnys+KNg+/bRDhRUqv
         4mFOtCp6g47kFduyBoj/NPxGqmCGEUhZT8pKA9IZTtlfr7umOfycANGkzProT66b7Vxa
         CH4w==
MIME-Version: 1.0
X-Received: by 10.194.52.68 with SMTP id r4mr371644wjo.8.1449590965365; Tue,
 08 Dec 2015 08:09:25 -0800 (PST)
Received: by 10.28.226.10 with HTTP; Tue, 8 Dec 2015 08:09:25 -0800 (PST)
In-Reply-To: <0a0a70d756b14a84fc1cd19fd04bb914@mail.gmail.com>
References: <0a0a70d756b14a84fc1cd19fd04bb914@mail.gmail.com>
Date: Tue, 8 Dec 2015 11:09:25 -0500
Message-ID: <CAAyV7nG0amKb9C3HRURFDRC=zWvmKRqJ6Ee2tv8KZNa2O2RdBw@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: PHP 5.6 Support Timeline
From: ircmaxell@gmail.com (Anthony Ferrara)

Zeev,

On Tue, Dec 8, 2015 at 10:14 AM, Zeev Suraski <zeev@zend.com> wrote:
> Following the initial discussion, I prepared an RFC that proposes to exte=
nd
> the support periods for PHP 5.6:
>
>
>
> https://wiki.php.net/rfc/php56timeline
>
>
>
> Thanks to Ferenc Kovacs and David Zuelke for reviewing it for any glaring
> omissions.
>
>
>
> Let the discussion continue=E2=80=A6

I'd prefer it if the RFC took a stance and made a recommendation to
one of the options. That way the discussion could be more guided
around the stance rather than simply generic. And also it makes the
votes easier to understand as it's more of a "yes/no" rather than
multiple options.

Overall, I fall into the 1 year maintenance, 2 year security camp.
That would put 5.6 EOL when 7.3 is out (approximately).

Thanks for putting it together.

Thanks.