Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75262
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-ID: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me>
Date: Sat, 5 Jul 2014 22:23:50 +0100
To: PHP <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: [RFC] Name of Next Release of PHP
From: ajf@ajf.me (Andrea Faulds)

Good evening,

I am announcing a rather unorthodox RFC.

With the advent of the phpng and uniform variable syntax RFCs, it looks =
likely the next major release of PHP, to succeed the 5.x series, may =
appear relatively soon. However, unlike with previous releases of PHP, =
it is not entirely clear what it shall be called.

This RFC attempts to settle the matter once and for all with a straight =
yes/no vote as to whether the name should be PHP 6. Should it pass, the =
matter is settled and we actually have a proper name for this fabled =
=93PHP NEXT=94. Should it fail, nothing is really lost, except that the =
discussion will inevitably resurface at some point. The plan, really, is =
to hopefully get it over with now so we don=92t have to have this =
discussion later, avoiding potential future bikeshedding or derailment.

This is the shortest RFC I=92ve ever authored, and I=92d greatly =
appreciate it if everyone read the whole thing:

https://wiki.php.net/rfc/php6

The plan for voting, if I think we should go ahead with it, is the same =
as a normal RFC: at least 2 weeks after proposed to internals, voting =
for at least 1 week.

Thanks!
--
Andrea Faulds
http://ajf.me/