Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73526
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <533C0713.9070106@eliw.com>
References: <533C0713.9070106@eliw.com>
Date: Wed, 2 Apr 2014 19:57:08 +0200
Message-ID: <CAF+90c9xc1cd8MFMmvj+VC_Q8gYms+vz+zRGjMV2aWPjV6svxw@mail.gmail.com>
To: Eli <eli@eliw.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c24b3869d04904f6130306
Subject: Re: [PHP-DEV] About PHP6 ...
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c24b3869d04904f6130306
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Apr 2, 2014 at 2:48 PM, Eli <eli@eliw.com> wrote:

> Hello everyone.  I've been hitting a lot of conferences recently, and
> found myself having the same discussion with multiple members of the
> community.  And many of them have 'heavily encouraged me' to bring this
> discussion up here.  And Julien's recent PHP6 email, reminded me that I
> hadn't done so.
>
> The short form is:
>
> We should not name the next version of PHP: PHP6, for 2 reasons:
>     1. It will cause confusion in those least able to adapt
>     2. It costs us nothing, hurts us in no way, to name it something else
>

There is potential for confusion regardless of what we do. If it's PHP 6,
we get conflicts with existing literature. If it's PHP 7, this will lead to
confusion about a version number being skipped. (Which is imho a pretty big
wtf moment.)

I find it quite ridiculous to break our versioning scheme over this kind of
nonesense.

Nikita

--001a11c24b3869d04904f6130306--