Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89774 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89970 invoked from network); 9 Dec 2015 17:59:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2015 17:59:54 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@daveyshafik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@daveyshafik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 209.85.213.53 cause and error) X-PHP-List-Original-Sender: me@daveyshafik.com X-Host-Fingerprint: 209.85.213.53 mail-vk0-f53.google.com Received: from [209.85.213.53] ([209.85.213.53:33968] helo=mail-vk0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C4/A8-20458-51C68665 for ; Wed, 09 Dec 2015 12:59:50 -0500 Received: by vkbs1 with SMTP id s1so59231689vkb.1 for ; Wed, 09 Dec 2015 09:59:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daveyshafik-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=4FHzUPIVX0BYiX6LSyPQv/vnmj1BRyELCRx8D2vzVoI=; b=SReJ6DZS9CVkmr0vb70W5ewY+dEaL2KhaLQohRvhtr+dHJ2ewoPni0izuu3yohFW0n tgPeZ11aY8Eksaqp93pwfNy4x7ruRf+gCgJPkIassvWDtHAEui8w70jcgMUBrhpixlha DeASNiSLXoJYN5XOlibk0WS4AlkLxvSTFffNiCQWpeo8Lohouk4MAI8mtmyg7CHYUFjK GucE4QDPXKvRZoY4m58mNcG9lvERZmhU6jdZRmf92eoDoy2ogdOJXuuTvKOkq1iRty+0 2hd/uMQyr9xzEzXHw245GAzeyp+kVG+dpVh562NCc8q5Xef3daDyyCJu0GvDloVItiHA HZ3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=4FHzUPIVX0BYiX6LSyPQv/vnmj1BRyELCRx8D2vzVoI=; b=U3iPgYyADzWxpnIuDm5F1L7WLRmVzQM2PlWkhta8W1km4uSow2uDnY4f8rteAjjc5Q 1GVf/vlCDuheeoN8swMyeUvhVrHRuxOKpr9pkWg3++0x9lfZvHkWkN9WQpAP2dg+PSFq yB25rGJVwwEs6PGjOCg3HpzgCyQs4nKWghqpClHAOSZoh2ag+7PZze4lsKk5+RNh8ing ISU0thySq7YW1XqIPAvSAF3ESBOSaxyhluo4JiGsc3lHijCw+zzEnXWhGdpcjaKruoDb fXsodHlcmGsnWzBa8UR/lry+oTZiBSZF5aFVPIKqP7qxaizdZIa8USDi+EJmMpjZmJyZ DBJg== X-Gm-Message-State: ALoCoQmQ33tsaQ9j2BOgGVw18d2XZR7g7yvkS3et6RABU2tRyYQFlTcHvICx8wAbIRd/9AKOsH7L757Q+uXUzUczwI1R0JlLl/clD8MXdzAXJdtAsEJAK6Y= MIME-Version: 1.0 X-Received: by 10.129.80.138 with SMTP id e132mr1410995ywb.90.1449683986436; Wed, 09 Dec 2015 09:59:46 -0800 (PST) Sender: me@daveyshafik.com Received: by 10.13.253.130 with HTTP; Wed, 9 Dec 2015 09:59:46 -0800 (PST) In-Reply-To: References: <0a0a70d756b14a84fc1cd19fd04bb914@mail.gmail.com> Date: Wed, 9 Dec 2015 12:59:46 -0500 X-Google-Sender-Auth: kw0f-8SRlpSSu10m54r3zfXHGNs Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary=001a1147fa520ca42a05267adb54 Subject: Re: [PHP-DEV] RFC: PHP 5.6 Support Timeline From: davey@php.net (Davey Shafik) --001a1147fa520ca42a05267adb54 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Frankly, I think the LTS distros that include PHP 5.6 will be plenty =E2=80= =94 as we've seen with 5.3, it has been maintained with back ports long after the official EOL. People either understand what they're getting into when making these choices, or they don't and they don't care anyway. I'd vote +1 on 2b. On Tue, Dec 8, 2015 at 7:07 PM, Pierre Joye wrote: > hi, > > On Wed, Dec 9, 2015 at 2:51 AM, Adam Howard > wrote: > > #3 all the way. Extending support only extends the excuse of poor habi= ts > > and encourages those habits. > > Same here. > > However, if I have to choose something I would like to understand why > all of a sudden December 31 become a valid date. It is unrelated to 7 > release date (December 3rd) and has no relevance whatsoever but easier > to remember. > > Given this, I would propose to either add, change or update the options > with: > > - makes 5.6 deadlines match 7 release date and support lifetime > . Active support until December 3rd 2017, > . Active support extended to one year, end December 3rd, 2017 > . And the options for the security support, one or two years > > - no change, as stick to what we clearly and openly define in the > lifecycle page (http://php.net/supported-versions.php) and extend > security support to 2 years (ending on 28 Aug 2018) > > I had to go with make the dates match with no change, eventually > adding one year for security support as I consider extending the > active support at this stage as a mistake and bad usage of our limited > resources. > > Cheers, > -- > Pierre > > @pierrejoye | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > --001a1147fa520ca42a05267adb54--