RE: [PHP-DEV] PHP 5.6 life cycle

> -----Original Message----- > From: Derick Rethans [mailto:derick@php.net] > Sent: Monday, December 07, 2015 12:41 PM > To: David Zuelke > Cc: Anatol Belski; Larry Garfield; internals@lists.php.net > Subject: Re: [PHP-DEV] PHP 5.6 life cycle > > On Mon, 7 Dec 2015, David Zuelke wrote: > > > On 06.12.2015, at 20:38, Anatol Belski <anatol.php@belski.net> wrote: > > > > > From today's perspective, I'd suggest to extend the security only period > of 5.6. > > > > That would be my suggestion too. > > > > End "full" support in, say, December 2016 (a year after 7.0.0), but > > then give it two years of security fixes instead of just one. > > I think that's indeed the most sensible option. Normal support to Dec 2106, > and security til 2018. Are you really suggesting to end security fixes 88 years before we end normal support? :) Typos aside, that's what I'm leaning towards as well. As I said in one of my initial notes, I think that ultimately what users care about primarily is the security support and less so about the 'full maintenance'. That's what defines the true lifetime of a version. Ferenc - do you still feel strongly that we should defer the decision into a later time? I want to know whether to include that as an option in the RFC. Personally - while there are pros and cons to both directions, I'm leaning more towards having a clearly defined timeline that we decide on in advance. Zeev