Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89754
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.45 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
In-Reply-To: <0a0a70d756b14a84fc1cd19fd04bb914@mail.gmail.com>
Date: Tue, 8 Dec 2015 16:18:43 +0100
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <C7F52D0F-7169-48D0-B0AC-9D755205E21B@heroku.com>
References: <0a0a70d756b14a84fc1cd19fd04bb914@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Subject: Re: [PHP-DEV] RFC: PHP 5.6 Support Timeline
From: dz@heroku.com (David Zuelke)

It just occurred to me (too late :D sorry Zeev) that it might make sense =
to split this into two RFCs:

- to define the active support end date for 5.6 (e.g. "2016-08-28" or =
"2016-12-02" or "2016-12-31")
- to define the security support end date for 5.6, and specify that =
relative to the active support end date only (e.g. "12 months after =
active support end date" or "24 months after active support end date")

That would also allow us to, if the need arises, change the active =
support end date sometime next year (for whatever reason; let's hope it =
is not necessary!) without having to open up a discussion about the =
security end date again ;)



> On 08.12.2015, at 16:14, Zeev Suraski <zeev@zend.com> wrote:
>=20
> Following the initial discussion, I prepared an RFC that proposes to =
extend
> the support periods for PHP 5.6:
>=20
>=20
>=20
> https://wiki.php.net/rfc/php56timeline
>=20
>=20
>=20
> Thanks to Ferenc Kovacs and David Zuelke for reviewing it for any =
glaring
> omissions.
>=20
>=20
>=20
> Let the discussion continue=E2=80=A6
>=20
>=20
>=20
> Zeev