Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89697 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92184 invoked from network); 7 Dec 2015 11:04:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2015 11:04:05 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.213.48 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.213.48 mail-vk0-f48.google.com Received: from [209.85.213.48] ([209.85.213.48:34381] helo=mail-vk0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F6/FE-55814-2A765665 for ; Mon, 07 Dec 2015 06:04:05 -0500 Received: by vkbs1 with SMTP id s1so100020263vkb.1 for ; Mon, 07 Dec 2015 03:04:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zend-com.20150623.gappssmtp.com; s=20150623; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=9ahMwAD8C4eSOOmCvlvsaPeumg/CFjAaulRktZNyiRw=; b=P0haq9nQqz/3FK2ayD1AZDmgkzHrcoJRCFbkdEBU8jXeiYnzdu8m7rlcO7yJOXt0rq Ye8utlopVjHNnR6gQva8U4RZbXTL4sqEoa5iY2HGkxr89F8llCLBIoCpCJLzFl02mIcc yPzN4WLGqD8+7mDYIhlemdygGXOcuVVGuA1EbudBYho07WmSumyReb15tZmTKhnsOCFm SC99yCVaKIifMSTbsWekABdNKYE/kHLXsOdITOEgCghFUDPenRw6rbjErFkoP7PsqkCx hxA59ljQK3Nr0SmeY58vJ9iyWLoJNbFJS+N6bGv2j3TkmvAj/409Y1D7ZBdSK5PBzPtx ZR4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=9ahMwAD8C4eSOOmCvlvsaPeumg/CFjAaulRktZNyiRw=; b=OnYlsk6qEBgf4XwlRzW7LNjotcTyOyprU0fq9ciSmsi4mg7qM1FNJI8+6vsbc7/ebm 1+kGAt/QcZky0tZ/R5TDN4Lhi/OZ4p+vsUcQgz2/E14+cqhVnNC4BVW4jm3ReKafqzkx C9UeV1dZUlO6t4ln9Igq4Sshbm41VJCVMWpo4qwmJ38RqVFj1KCF1a2U7enS7UXD4WsS zttSp+AgffCQ1SmLqqAo/xc1gClRdXMoWHj8hVqCXgBPnm4z9ZPMljjitmf0uYhffUkK +S0kkD+DuWEfhkNXNb+7QgjHowMjlZwbUZyt1nQRVE2hMObQxr3dC0LwAP9WiJ3GWWzZ IZHg== X-Gm-Message-State: ALoCoQk0jleGVKxA82MCaV5GYrrNsdsgL07aAEvHoZ0auAi8ERxrl47bWCP8hIlXicFdeJ8uFaniYJewai9nwoym1CLqU1VOUVO19pnLp4rRody7Nb5xsYexUQMpdcvNoaLiwPbnKPU9QmkyAGpo5yqlwGWrlmMAv9cVSiqFZTb2vYJpmcGkyCU= X-Received: by 10.31.3.162 with SMTP id f34mr21203663vki.15.1449486239828; Mon, 07 Dec 2015 03:03:59 -0800 (PST) References: <566485DD.7010504@garfieldtech.com> <012901d1305d$aa68ed30$ff3ac790$@belski.net> <1B431280-0C1A-4426-8F9E-C07F3ECA773F@heroku.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHgh9Y9UJHbSHpdKU+NswaLC82f2wIq/m6HAMeq+ucCFzVLDwJ+ORzvAc6WXQMByRn+dgE/xg+7nj2wozA= Date: Mon, 7 Dec 2015 13:03:58 +0200 Message-ID: To: Derick Rethans , David Zuelke , Ferenc Kovacs Cc: Anatol Belski , Larry Garfield , internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] PHP 5.6 life cycle From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Derick Rethans [mailto:derick@php.net] > Sent: Monday, December 07, 2015 12:41 PM > To: David Zuelke > Cc: Anatol Belski; Larry Garfield; internals@lists.php.net > Subject: Re: [PHP-DEV] PHP 5.6 life cycle > > On Mon, 7 Dec 2015, David Zuelke wrote: > > > On 06.12.2015, at 20:38, Anatol Belski wrote: > > > > > From today's perspective, I'd suggest to extend the security only period > of 5.6. > > > > That would be my suggestion too. > > > > End "full" support in, say, December 2016 (a year after 7.0.0), but > > then give it two years of security fixes instead of just one. > > I think that's indeed the most sensible option. Normal support to Dec 2106, > and security til 2018. Are you really suggesting to end security fixes 88 years before we end normal support? :) Typos aside, that's what I'm leaning towards as well. As I said in one of my initial notes, I think that ultimately what users care about primarily is the security support and less so about the 'full maintenance'. That's what defines the true lifetime of a version. Ferenc - do you still feel strongly that we should defer the decision into a later time? I want to know whether to include that as an option in the RFC. Personally - while there are pros and cons to both directions, I'm leaning more towards having a clearly defined timeline that we decide on in advance. Zeev