Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75285 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15621 invoked from network); 6 Jul 2014 15:19:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jul 2014 15:19:41 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.200 imap1-2.ox.privateemail.com Received: from [192.64.116.200] ([192.64.116.200:53753] helo=imap1-2.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C7/B0-12239-C0969B35 for ; Sun, 06 Jul 2014 11:19:41 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id CF9F2B00085; Sun, 6 Jul 2014 11:19:37 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap1.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap1.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VVX0VN9idFmj; Sun, 6 Jul 2014 11:19:37 -0400 (EDT) Received: from andreas-air.home (host86-172-51-137.range86-172.btcentralplus.com [86.172.51.137]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 23219B0007B; Sun, 6 Jul 2014 11:19:35 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) In-Reply-To: <53B9675F.5030605@gmail.com> Date: Sun, 6 Jul 2014 16:19:29 +0100 Cc: kris.craig@gmail.com, internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: References: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me> <650742796f119ed972a688a58e02242b@mail.gmail.com> <1e8b4df08c14971746946ed85ca8fa22@mail.gmail.com> <53B9675F.5030605@gmail.com> To: Jocelyn Fournier X-Mailer: Apple Mail (2.1878.2) Subject: Re: [PHP-DEV] [RFC] Name of Next Release of PHP From: ajf@ajf.me (Andrea Faulds) On 6 Jul 2014, at 16:12, Jocelyn Fournier = wrote: > It's my first post in this list, and wanted to share my external point = of view, with a parallel with the MySQL world. Welcome to PHP! :) > MySQL 6 was alpha in 2007 and finally was never released. > So far its name has never been reused (instead we had MySQL 5.6 and = 5.7 to avoid confusion, and there are also books about PHP 6 / MySQL 6) > Even on the MariaDB side, they bumped up the version to 10.0 to avoid = confusion (and because it was not based on MySQL 5.6). Similarly, ECMAScript 4, which was to be the replacement for ECMAScript = 3, was abandoned and skipped, with ECMAScript 5 replacing it and = ECMAScript 6/Harmony continuing it in spirit. There is some precedent = for this. > There are quite a few tutorials and reference about PHP 6 on the web, = it would be misleading to have something completely different, but with = the same name as the "old" PHP 6. However I'm not convinced "7" is the = right choice, perhaps a radical change in version number would be better = ? Well, 7 is a nice number. But yes, a more radical change might be = better. How about PHP 14, after the year? PHP Loxodonta, a genus of = elephants? PHP 14.mm, where mm is the month, following the Ubuntu = month/year scheme? However, all other options only seem to have fringe support at the = moment, so a binary 6/7 vote is optimal, unless you can find a name = everyone can agree on. Keeping with 6 or 7 means we stick to our tried = and tested naming scheme, too. I think that=92d be for the best. Side note: another thought comes to me now that just skipping 6 and = going to 7 makes little sense in a way, as 7 isn=92t the successor to 6, = it is the second successor to 5, the first (the old PHP 6) having been = abandoned. -- Andrea Faulds http://ajf.me/