Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75721 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66059 invoked from network); 20 Jul 2014 16:11:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jul 2014 16:11:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=andi@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=andi@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.53 as permitted sender) X-PHP-List-Original-Sender: andi@zend.com X-Host-Fingerprint: 209.85.220.53 mail-pa0-f53.google.com Received: from [209.85.220.53] ([209.85.220.53:32809] helo=mail-pa0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F0/73-48607-54AEBC35 for ; Sun, 20 Jul 2014 12:11:51 -0400 Received: by mail-pa0-f53.google.com with SMTP id kq14so8182346pab.26 for ; Sun, 20 Jul 2014 09:11:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=zLIAAcfOFm2FE0AG8W0se6nk7xt0r4jS3qwZPAcX5RU=; b=AbdGIYp2up5rSld1XxMltFxnrqxVVakoVH7q0JgevkLcilYCLlR2lvL3o0z1ITc1AX XjvThN07kDM6QxYI/y6FagE8OiOBUt0+hu6900gEnhTKUgWCYnfvGr1eacIsGIZ/srkW BKH+Azi4wbZInoaxLzMYciMlrVFYcg3JeWL6v/Djz9Z/A5kWh9gg22HoVMqayWXnvqlF tAoLosnbaS8rXHU/rbnhCJHmleYVZeOkYAy9KEtSOi1/FHvLvJaK3zfVgJzCJo35y47A wXtGSgIRtdHrHshqWjxexHlw2n/8iZYr6P/uvr7UU31QSX5Gd7pD8md2VcVuXsSqkgxf o3sQ== X-Gm-Message-State: ALoCoQnvQGOD9+qJc7mhl9nzk0UdOXxooGhQ8yHvsLsIknCRo3VAVzEQM2cL8x2DbQA46kmj9Aisw+ZRBHfu0JRCoGEBhW6ngUNrnTFg6v3IhuXobG4ydeHISzpGim9W+4H18p4vNcLM X-Received: by 10.68.167.133 with SMTP id zo5mr8513312pbb.21.1405872707277; Sun, 20 Jul 2014 09:11:47 -0700 (PDT) Received: from [192.168.1.112] (c-24-130-225-174.hsd1.ca.comcast.net. [24.130.225.174]) by mx.google.com with ESMTPSA id tl3sm47406286pac.41.2014.07.20.09.11.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Jul 2014 09:11:45 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: Date: Sun, 20 Jul 2014 09:11:43 -0700 Cc: Andrea Faulds , PHP Internals X-Mao-Original-Outgoing-Id: 427565503.393586-bcb0851ed38bf405f852f48560a8dada Content-Transfer-Encoding: quoted-printable Message-ID: <2F941D55-DC95-4454-AD53-D58B729EF32B@zend.com> References: <84603C6F-F984-4F73-892A-4416391E4769@ajf.me> To: Peter Cowburn X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] [VOTE][RFC] Name of Next Release of PHP From: andi@zend.com (Andi Gutmans) On Jul 20, 2014, at 8:39 AM, Peter Cowburn = wrote: >=20 > As for the PHP 7 section, this is by far the dominant part of the RFC. = Both > in terms of physical presence, but also points and counter-points. >=20 > It also contains, IMO unnecessarily, light-hearted and jokey comments = not > befitting an RFC =97 unless you see the RFC as a joke too ;) =97 = about 6 being > a failed version in other software, and 7 a lucky number. Seriously?.. >=20 > The RFC as a whole is very light on trying to summarise, or at least > provide reference to, the history of "PHP 6=94 and discussions around = it. > This is disappointing, if the aim was to see a balanced summary of = previous > discussions. However, this particular gripe is a common issue with = our > RFCs as a whole. >=20 > Personally, regardless of the content of the RFC, I feel that the = choice is > obvious. I=92m just a little concerned about the lack of quality from = both > =93sides=94 in presenting their argument(s), or not. I actually think that both perception and facts need to be take into = account on naming/version number decisions. I must say I do share the perception that many version 6=92s in = open-source have been failures and I=92ve heard many people ridiculing = the PHP 6 is like Perl 6. So I don=92t think it=92s irrelevant. - This = is perception but it matters. Fact - There is SO much PHP 6 content out there and many folks think = they know what PHP 6 is that I think the confusion we=92d be creating in = calling this PHP 6 would be huge and unnecessary. To the point I am even = surprised we have folks here who are resisting not calling it PHP 6. It = feels pretty obvious to me that we are doing people a disservice calling = it PHP 6. But anyway, didn=92t want to restart the discussion but just wanted to = point out that RFC should address both perception and fact because both = matter. It=92s not just a technical discussion. Andi