Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79702 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73410 invoked from network); 16 Dec 2014 09:01:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2014 09:01:01 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:52488] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 73/00-07463-9C4FF845 for ; Tue, 16 Dec 2014 04:00:59 -0500 Received: (qmail 29977 invoked by uid 89); 16 Dec 2014 09:00:04 -0000 Received: by simscan 1.3.1 ppid: 29893, pid: 29970, t: 0.0779s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.178.188.220) by mail4.serversure.net with ESMTPA; 16 Dec 2014 09:00:04 -0000 Message-ID: <548FF48A.7000605@lsces.co.uk> Date: Tue, 16 Dec 2014 08:59:54 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] PHP 5.7 From: lester@lsces.co.uk (Lester Caine) On 16/12/14 07:29, Levi Morrison wrote: >>> There has been some debate about whether to make “PHP 5.7". I have made a very simple RFC. It proposes a final minor version of PHP 5, PHP 5.7, to be released at the same time as PHP 7, with no new features whatsoever. >>> >> >> > I am wondering why we need that? no new features.... >> > >> > I think we can extend 5.6 release cycle to avoid that.. > Extending the PHP 5.6 release cycle doesn't give an opportunity to > raise different E_STRICT and E_DEPRECATED messages in preparation for > PHP 7.0. This may or may not be something you value, but it's > something I personally value. +1 Leave 5.6 as a 'clean' version so stability is retained. 5.7 is an optional stepping stone to help upgrade code, but for users of frameworks will have their content migrated from an older platform to a clean PHP7 one. It is only those users who have personal code that need help migrating. 5.7 would have sub versions as particular problems are identified in the migration process rather than encumbering PHP7 with unnecessary bloat? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk