Re: RFC: PHP 5.6 Support Timeline
| From: | David Zuelke | Date: | Tue, 08 Dec 2015 15:18:43 +0000 |
| Subject: | Re: RFC: PHP 5.6 Support Timeline | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-89754@lists.php.net to get a copy of this message | ||
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:
>
> Following the initial discussion, I prepared an RFC that proposes to extend
> 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…
>
>
>
> Zeev