Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73559
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain jonstirling.co.uk from 209.85.215.47 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAEZPtU6eQZJnz1u3K5Ws5bNNhGmprjbhYhO4bGcysJFxdvCMZg@mail.gmail.com>
References: <533C0713.9070106@eliw.com>
	<CAEZPtU6eQZJnz1u3K5Ws5bNNhGmprjbhYhO4bGcysJFxdvCMZg@mail.gmail.com>
Date: Thu, 3 Apr 2014 11:02:06 +0100
Message-ID: <CAPgKKxWTrJP4mfEXpi=P-R-GomdiP-JBqNTCiuX4+_+MnUgQTA@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Eli <eli@eliw.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01227abc64a49f04f6207e15
Subject: Re: [PHP-DEV] About PHP6 ...
From: phoenix@jonstirling.co.uk (Jonny Stirling)

--089e01227abc64a49f04f6207e15
Content-Type: text/plain; charset=ISO-8859-1

Hi all.

Let put things in perspective:
> - PHP 6-dev (the -dev part is important here) was killed 5 years ago
> (or maybe more, did not check the exact time)
> - book about it have been released, how it is remotely related to us
> is a mistery but let consider them as valid...
>   . Current idea is to get 6 out in ~ two years. Making these books
> like 7-8 years old by the time php 6 will be released
>   . The communication about the development of php 6 will outcome any
> legacy results in google/bing and other
>   . The couple of books still on sale are likely to be removed (if not
> already, as I never saw one except ebook, and really, anyone buying 5
> years old book in tech ...)
>

Calling it 6 in the first place was potentially the mistake, one we maybe
shouldn't make a second time.

At the moment, PHP.next doesn't really exist. What it will eventually be
called is surely a question for when we get around to distributing it, e.g.
shortly before first alpha. Until then (imo) there is no benefit to
deciding this now, or in the near future. Any use of names PHP6 or PHP7 or
even PHP8 before it exists is just going to continue the issues brought up
here in the future.

That being the case, perhaps keeping the naming as simply php.next (branch
included) or using basic code names is the way to go. This should stop
people getting confused in the future if a branch doesn't make it to
release (no version number), or people decide to write about it (obvious
that it's not release).

Just another 2 cents. In the mean time as Pierre says, there's still time
better spent noting down ideas for php.next.

Cheers.
Jonny.

--089e01227abc64a49f04f6207e15--