On May 25, 2010, at 4:44 AM, Ford, Mike wrote:
>> -Original Message-
>> From: Philip Olson [mailto:phi...@roshambo.org]
>> Sent: 19 May 2010 05:44
>> To: PHP Documentation ML
>
>
>> Two new entities being proposed:
>> - version.trunk.after.53
>> "This is in Subversion trunk only, and
> -Original Message-
> From: Philip Olson [mailto:phi...@roshambo.org]
> Sent: 19 May 2010 05:44
> To: PHP Documentation ML
> Two new entities being proposed:
> - version.trunk.after.53
>"This is in Subversion trunk only, and will probably exist as of
> PHP 5.4 or 6.0."
Brilliant id
On Wed, May 19, 2010 at 06:44, Philip Olson wrote:
> Two new entities being proposed:
> - version.trunk.after.53
> "This is in Subversion trunk only, and will probably exist as of PHP 5.4 or
> 6.0."
> - version.trunk.changelog
> "Future"
Do we need both?
The changelogs only list the versi
On 05/19/2010 06:45 AM, Daniel Convissor wrote:
Hi Philip:
Nobody knows if/when PHP 5.4 or PHP 6 will exist, yet commits are happening in
php-src/ trunk. We need to figure out how to document this stuff in such a way
that we:
...
Here's a proposal that may work, please critique:
Looks g
Hi Philip:
> Nobody knows if/when PHP 5.4 or PHP 6 will exist, yet commits are happening
> in php-src/ trunk. We need to figure out how to document this stuff in such a
> way that we:
...
> Here's a proposal that may work, please critique:
Looks good. Thanks for thinking about this stuff.
--D
Nobody knows if/when PHP 5.4 or PHP 6 will exist, yet commits are happening in
php-src/ trunk. We need to figure out how to document this stuff in such a way
that we:
- will inform users
- won't confuse users
- utilize our changelogs
- won't repeat the PHP 6 fiasco
Here's a proposal that ma
