Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76584 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42768 invoked from network); 16 Aug 2014 09:10:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Aug 2014 09:10:36 -0000 Authentication-Results: pb1.pair.com header.from=thomas@nunninger.info; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=thomas@nunninger.info; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain nunninger.info from 87.106.55.207 cause and error) X-PHP-List-Original-Sender: thomas@nunninger.info X-Host-Fingerprint: 87.106.55.207 mail.nunninger.info Linux 2.6 Received: from [87.106.55.207] ([87.106.55.207:40123] helo=mail.nunninger.info) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A1/50-38696-9002FE35 for ; Sat, 16 Aug 2014 05:10:35 -0400 Received: from pd95c6425.dip0.t-ipconnect.de ([217.92.100.37] helo=[192.168.178.30]) by mail.nunninger.info with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1XIZzq-00030r-KW; Sat, 16 Aug 2014 09:10:15 +0000 Message-ID: <53EF1FE6.4020103@nunninger.info> Date: Sat, 16 Aug 2014 11:09:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Pierre Joye , David Soria Parra CC: PHP internals References: <5C97D818-4616-440D-9C0D-B9F9C8D034DC@ajf.me> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.3 (-) X-Spam-Several-Recipients: Yes Subject: Re: [PHP-DEV] Let's make a 5.7 release From: thomas@nunninger.info (Thomas Nunninger) On 08/16/2014 12:52 AM, Pierre Joye wrote: > On Sat, Aug 16, 2014 at 12:49 AM, David Soria Parra wrote: >> On 2014-08-15, Pierre Joye wrote: >> Let me summerize a few things that have come up: >> >> (1) phpng doesn't justify PHP7 >> It does. It's a complete new engine. It has performance improvements. Where >> do you draw the line of what justifies a PHP 7? It's a major BC break and we >> needd a major version for it > > > No it does not. Even if it would do, that's not something I can live > with in the next 10 years. As I repeatedly said, with explanations > why. Just a heretical question from someone who has no clue about PHP core: What speaks against having PHP 8 one or two years after PHP 7? I like the idea of - having PHP 5.7 introducing deprecation warnings without additional features (and perhaps some cleanings regarding the spec?) - full concentration on PHP 7 regarding phpng (including AST & co) and cleanings according to the spec. - PHP 8 with other improvements that are currently planed for PHP 7. (Perhaps it's even possible to introduce most deprecation warnings of planned changes for 8 in 7 and 5.7.) Regarding adoption: Agile teams/projects are able to follow the path from 5.6 to 5.7 (if needed) up to 7 and 8. Slow teams/projects can migrate from 5.6 to 5.7 "easily" and later to 8. Adoption to PHP 7 would not be a KPI of the PHP project. Regarding branch maintenance: Support for 5.7 could be extended and for 7 could be shortened if announced early enough (latest at GA of 7.0). Regarding PHP project's project management: That would be release early, release often. Of course, extensions need to be changed twice for PHP 7 and 8 - but the amount of changes should be almost the same. A side note regarding the spec: I would not waste time to write/discuss a formal spec that describes all oddities of 5.6/7 or force 5.6/7 to follow a spec too much. The perspective of the spec is PHP 7 that is the first version where compliance to the spec is needed. (Probably Facebook has other plans. But I think one year to get it right on both sides - the spec and the implementation - is totally ok.) Regards Thomas