Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64225 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78976 invoked from network); 10 Dec 2012 12:57:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Dec 2012 12:57:06 -0000 Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 217.114.211.66 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:41113] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 96/C3-60401-02CD5C05 for ; Mon, 10 Dec 2012 07:57:05 -0500 Received: from [192.168.2.20] (host-188-174-210-58.customer.m-online.net [188.174.210.58]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 7B22D65014; Mon, 10 Dec 2012 13:57:01 +0100 (CET) To: Adam Harvey Cc: PHP internals list In-Reply-To: References: <1355137083.3178.24.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Organization: PHP Development Team Date: Mon, 10 Dec 2012 13:51:19 +0100 Message-ID: <1355143879.3178.37.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] PHP 5.3 - end of live schedule From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hi, On Mon, 2012-12-10 at 20:21 +0800, Adam Harvey wrote: > At the very least, I think we should keep full support going until > 5.5.0 final is out, which it strikes me probably won't be in February > at our current rate. > > Beyond that, I don't particularly want to create a rod for our own > backs ($DEITY knows, _I'm_ useless at merging across branches, as you > all know), but I wonder if 5.3 might need a bit longer in one form or > another. RHEL 6, Debian 6, Ubuntu 12.04 (not the latest stable > version, unlike the others, but the LTS version), Mac OS X 10.8 (and > many of the derivatives of these distros, particularly RHEL) are all > shipping PHP 5.3 packages by default. As a result, I think the odds > are that developers are likely to develop and deploy applications on > PHP 5.3 for quite some time to come. (Plus, 5.3 had most of the big > headline features of the last few years — a lot of people will > consider it "good enough".) > > I'm not suggesting we necessarily extend full support, but I wonder if > one year of critical bug fixes and security updates will be enough. In my opinion key for this is PR. Get people to migrate to 5.4. We are still flexible to interpret what "critical" issues are, and to merge and release those. (And extend that time if we see too little migration) For distributions at least Ondřej supported this option from Debian perspective. In my opinion distributions in fact would be happy with this. all they want are "critical" fixes in their "stable" and backport only this. The more we prefilter the simpler for them. Please also mind: Most bugs exist for years, most are older than 5.3. If they lived with those on 5.2 they are no stoppers to migrate away from there. The biggest category of 5.3-only bugs is around gc. PHP 5.3 won't stop working and for operations there is no big difference after February 2013 ... rather less risk of getting bug fixes which, by accident, change behavior. Therefore after February 2013 users updating need less validation when updating. johannes