Re: What to do with PHP 6
| From: | Daniel Egeberg | Date: | Wed, 31 Mar 2010 09:27:58 +0000 |
| Subject: | Re: What to do with PHP 6 | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969381508@lists.php.net to get a copy of this message | ||
On Wed, Mar 31, 2010 at 09:16, Jordi Boggiano <j.boggiano@seld.be> wrote:
> On Wed, Mar 31, 2010 at 9:49 AM, Philip Olson <philip@roshambo.org> wrote:
>> (d) Write "Future PHP Release" or similar until we know (seems okay)
>>
>> I lean towards (d) for most cases. Thoughts?
>
> I'd also prefer D since it is the easiest to search & replace once
> decisions are made. I think however that instead of Future PHP
> Release, which sounds really vague and timeless, I'd suggest deciding
> upon a name that everyone uses to talk about the next php, the obvious
> PHP.Next seems to be almost a standard now, we could make it more
> phpey with \PHP::Next or something, but I don't mind too much either
> way. This is still a bit vague and timeless, but it sounds cooler and
> it sounds like it's coming next, not "once upon a time in the future".
Why not just call it trunk?
--
Daniel Egeberg