Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58517 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68592 invoked from network); 2 Mar 2012 19:06:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2012 19:06:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=kris.craig@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kris.craig@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender) X-PHP-List-Original-Sender: kris.craig@gmail.com X-Host-Fingerprint: 74.125.82.54 mail-ww0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:50635] helo=mail-ww0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A5/89-22821-74A115F4 for ; Fri, 02 Mar 2012 14:06:48 -0500 Received: by wgbdq13 with SMTP id dq13so1713411wgb.11 for ; Fri, 02 Mar 2012 11:06:45 -0800 (PST) Received-SPF: pass (google.com: domain of kris.craig@gmail.com designates 10.216.137.147 as permitted sender) client-ip=10.216.137.147; Authentication-Results: mr.google.com; spf=pass (google.com: domain of kris.craig@gmail.com designates 10.216.137.147 as permitted sender) smtp.mail=kris.craig@gmail.com; dkim=pass header.i=kris.craig@gmail.com Received: from mr.google.com ([10.216.137.147]) by 10.216.137.147 with SMTP id y19mr2045649wei.5.1330715205093 (num_hops = 1); Fri, 02 Mar 2012 11:06:45 -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; bh=2b942y0IjYY+Y+ZRJV5F84bit9Te7icN6F8iB8pH4tY=; b=ovw8q25fA0skweOZ8Fkqlqjna8R3ExACgebiOKTO14TXK6yqTVca0VTJ68PrjcXSuI FsM/MLcCDyX+57Le34Xdrv1e9jkJGGDVbN2zTCIK3S1CGFJuTVu9mwtHzs9WRXrxO/QU DsPOuZ/K1zoEEI0GI1E+/IHMEQqrdkhci36de5ThAHvglXK+pTpRSfTmppgZ/021H6C8 dhm1rk1AZ3sluGVpgh4BsunzbxSx9enK1NXPV7omK/FmjVNkMjejgSKN9/cvy9N+j639 rU3YHhDeUkdBqFp1723Lo1t5wzKzT8JJwRwP8iT3fIT7f0W1IwAjwnOKM9bKzTSPmzt2 HY2A== MIME-Version: 1.0 Received: by 10.216.137.147 with SMTP id y19mr1642441wei.5.1330715204999; Fri, 02 Mar 2012 11:06:44 -0800 (PST) Received: by 10.223.75.146 with HTTP; Fri, 2 Mar 2012 11:06:44 -0800 (PST) In-Reply-To: References: <4F50EA41.1080706@php.net> <1330709339-sup-799@fewbar.com> Date: Fri, 2 Mar 2012 11:06:44 -0800 Message-ID: To: Pierre Joye Cc: Clint Byrum , internals Content-Type: multipart/alternative; boundary=00504502caea175cd604ba47473d Subject: Re: [PHP-DEV] [RFC] discussions, about a 5.3 EOL From: kris.craig@gmail.com (Kris Craig) --00504502caea175cd604ba47473d Content-Type: text/plain; charset=ISO-8859-1 Ok, I'm up to speed now. I agree that Option 1 is the best approach. --Kris On Fri, Mar 2, 2012 at 10:58 AM, Pierre Joye wrote: > again, we have a clear EOL process now for 5.4 and later. > > Only 5.3 does not have any. We have to define it now instead of doing > it in 1-2 years without giving our users any kind of reasonable delay > to plan a migration. > > Cheers, > > On Fri, Mar 2, 2012 at 7:54 PM, Kris Craig wrote: > > I'm probably missing something, but why not just do it like we did with > > 5.2? I.e. we keep maintaining it until PHP 5.5, at which time we > deprecate > > it and be done with it? > > > > Like I said, I'm probably missing something lol, so if someone could > > explain why this is different I'd be much obliged! =) > > > > --Kris > > > > > > On Fri, Mar 2, 2012 at 9:39 AM, Clint Byrum wrote: > > > >> Excerpts from Sebastian Bergmann's message of Fri Mar 02 07:41:53 -0800 > >> 2012: > >> > On 03/02/2012 07:34 AM, Pierre Joye wrote: > >> > > https://wiki.php.net/rfc/php53eol > >> > > >> > I discussed with Arne Blankerts and Stefan Priebsch over breakfast > >> today > >> > and Stefan had an interesting idea: why not announce (now) that PHP > 5.3 > >> > will go into EOL a year after PHP 5.5 comes out? > >> > > >> > * Now until PHP 5.5 comes out: bug and security fixes for PHP 5.3 > >> > * From the release of PHP 5.5: security fixes for PHP 5.3 for a > year > >> > > >> > Ideally, PHP 5.5 would be out in a year from now, so it would come > down > >> > to one year of bug and security fixes and one year of security fixes > >> > only. Makes sense to me. > >> > > >> > >> Just chiming in from the Ubuntu side of things. I think this is the most > >> predictable, and helpful plan for users and for distributors. > >> > >> From the user standpoint, its quite useful to know where you stand > >> for upgrade path. This should make conservative users comfortable with > >> using 5.3 on existing projects until 5.5 enters RC phase, and then they > >> can start evaluating their options to move to 5.5 or 5.4, as they know > >> they'll have a whole year to evaluate 5.5. If you put a clock on 5.3, > >> and 5.5 slips for legitimate reasons, then they'll be stuck with 5.4 > >> only, and you may actually *miss* the opportunity to get people on the > >> latest release. > >> > >> From a distribution standpoint, anything that lengthens the amount of > time > >> that PHP as a project fully supports a release makes our burden smaller, > >> and gives our users a better chance at having stable software for the > >> entire life of our LTS releases. Selfish, I know, but just stating the > >> obvious fact. > >> > >> -- > >> PHP Internals - PHP Runtime Development Mailing List > >> To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > > > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org > --00504502caea175cd604ba47473d--