Re: Next major version must be 7 (Lessons learned from the ECMAScript committee)

From: Date: Sat, 13 Mar 2010 22:08:12 +0000
Subject: Re: Next major version must be 7 (Lessons learned from the ECMAScript committee)
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-47247@lists.php.net to get a copy of this message
On Mar 13, 2010, at 1:56 PM, Lukas Kahwe Smith wrote:

> 
> On 13.03.2010, at 22:52, Stefan Marr wrote:
> 
>> 
>> On 13 Mar 2010, at 22:43, Sebastian Bergmann wrote:
>> 
>>> Rasmus Lerdorf wrote:
>>>> No, not ok.  We will call the next release whatever we like.  People who
>>>> have written books or articles about PHP 6 inferring they knew what the
>>>> final state of PHP 6 would be were misguided.  We never got to the point
>>>> of a final feature set much less a release date.
>>> 
>>> +1
>>> 
>>> Authors that wrote, publishers that published and readers that bought
>>> books on PHP 6 need to be ... punished ;-)
>> Is that wise and well-considered or something the community might regret in the long run?
> 
> 
> Nobody needs to be punished and I think Rasmus stayed clear of such words for a reason. The
> name of the next version is not really all that relevant more if the next version will be a minor
> bump (aka x.y+1) or a major (aka x+1.y).

The PHP manual refers to "PHP 6" over 200 times, and there are probably a few people
who've written code that takes this information into account. I'm not saying the proposal
in this thread is a solution or needed, but there is a valid concern here.

The PHP manual will be updated once this is figured out, with extra care ensuring unicode and PHP 6
information is current. All suggestions for how to handle this today are welcome.

Regards,
Philip


Thread (18 messages)

« previous php.internals (#47247) next »