Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58602
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Matthew Weier O'Phinney <weierophinney@php.net>
Cc: internals@lists.php.net
In-Reply-To: <F9.D1.35539.46BD45F4@pb1.pair.com>
References:
	 <CAEZPtU7qpMr9ZTX=+NDus05WA2RZ9A3rWNnHSr8WOBXjqbp4VQ@mail.gmail.com>
	 <F9.D1.35539.46BD45F4@pb1.pair.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 05 Mar 2012 16:42:33 +0100
Message-ID: <1330962153.3108.9.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] discussions, about a 5.3 EOL
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2012-03-05 at 10:27 -0500, Matthew Weier O'Phinney wrote:
> On 2012-03-02, Pierre Joye <pierre.php@gmail.com> wrote:
> > It should have been done before 5.4.0 was out, but better late than never.
> >
> > I put together four options here:
> >
> > https://wiki.php.net/rfc/php53eol
> >
> > I'm in favor of option #1, as it gives enough time to our users to
> > migrate by reducing the maintenance period to only one year.
> >
> > Suggestions or comments welcome,
> 
> Considering that 5.3 adoption is still eclipsed by 5.2 adoption, to be
> honest, it feels like doing 1 year bugfix + 1 year security fix is the
> minimum necessary. By the time we get good adoption of 5.3, it will
> already be EOL'd. :-/

Users can jump directly to 5.4, too.
Yes, I know (Linux) Distributions are conservative and slow and start
supporting 5.3 just right now. But well, we have limited resources,
only, too.

johannes