Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58478 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52693 invoked from network); 2 Mar 2012 13:04:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2012 13:04:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.161.170 mail-gx0-f170.google.com Received: from [209.85.161.170] ([209.85.161.170:43079] helo=mail-gx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F7/6E-11220-065C05F4 for ; Fri, 02 Mar 2012 08:04:33 -0500 Received: by ggmb2 with SMTP id b2so144850ggm.29 for ; Fri, 02 Mar 2012 05:04:30 -0800 (PST) Received-SPF: pass (google.com: domain of pierre.php@gmail.com designates 10.236.72.230 as permitted sender) client-ip=10.236.72.230; Authentication-Results: mr.google.com; spf=pass (google.com: domain of pierre.php@gmail.com designates 10.236.72.230 as permitted sender) smtp.mail=pierre.php@gmail.com; dkim=pass header.i=pierre.php@gmail.com Received: from mr.google.com ([10.236.72.230]) by 10.236.72.230 with SMTP id t66mr13206649yhd.45.1330693470625 (num_hops = 1); Fri, 02 Mar 2012 05:04:30 -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:content-transfer-encoding; bh=BB4fylC4mkou8Cizv3EcaKRJkMJz0LQ0CMPEMk0sYm8=; b=Y94qRhd8iY2FpNIZuhzY0lhMPj3wxijyOB/Xz4woSKkheV/GAXeS4BFymAHH53faWd P3SEjg1/8YpyZ+BpxY2WiWU7ZvWZG1vYpnuj4Rk6I2jc4ggA/fCGHWxulC9b2oBSHfue 0gMJsnOIdBLvIiz6YZo2BXMrFLiIi0TIgGNzZc7jtgPMHRwh3ABaaLG6UUKaAwh9Tpc4 KP4x2WH2roci1V0UPb478Bic7ExENR2fZ4I+wJYIsuskTXuS7wrnSV8/TMlkOhCFaxv4 EylqWxfmz6p3yG0BzM0whA1yLFhz4uZ85SChvvoF5iUuZiGmFwGP8vvJBTk9DZDfpM4W YLEg== MIME-Version: 1.0 Received: by 10.236.72.230 with SMTP id t66mr10426509yhd.45.1330693470572; Fri, 02 Mar 2012 05:04:30 -0800 (PST) Received: by 10.146.221.14 with HTTP; Fri, 2 Mar 2012 05:04:30 -0800 (PST) In-Reply-To: References: Date: Fri, 2 Mar 2012 14:04:30 +0100 Message-ID: To: Anthony Ferrara Cc: Keloran , PHP internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] discussions, about a 5.3 EOL From: pierre.php@gmail.com (Pierre Joye) Hi, We already discussed LTS On Fri, Mar 2, 2012 at 2:00 PM, Anthony Ferrara wrote= : > Would it be worth while to discuss the possibility of LTS releases > (Long Term Support) with 5 or 7 year support (from time of initial > release)...? > > 5.3 is 2.5 years old now. =A0Which means depending on the option that's > chosen here, it'll be completely out of support a mere 3.5 to 4.5 > years after initial release. =A0For a platform or program, that's fine. > But for a programming language, that seems a bit... =A0short. > > Instead, I'd like to see at least one current release be "LTS", or > "extended support" which would then be covered by security fixes (at > the very least) for at least 5, and possibly 7 or even 10 years after > initial release. It has been discussed already and it is impossible to do from our sides. RHEL, SEL or other distros do that on their side. For us, https://wiki.php.net/rfc/releaseprocess matters now. And the idea is how can we make 5.3 fits into that while having released before this RFC was approved. Please keep in mind that no matter the option, we will be over 3 years, that's pretty good (given too that 5.4 is almost 100% BC). Cheers, --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org