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 may work, please critique: For changed stuff: - Add everything in trunk to changelogs, like we do elsewhere - Make the version of these changes be entities - The entity used is minor php version specific, so today: &version.trunk.after.53; - Example: New parameters are added as normal, with a 'special' changelog entry For new stuff: - Also &version.trunk.after.53; - Note: reference/*/versions.xml files are not translated And when 5.4 and/or 6.0 is released: - Replace entities with standard text (in en/) or more appropriate entities - Not simply leave these entities in the docs with new values 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" Example [pseudo] usage: <changelog> <entry>&version.trunk.changelog;</entry> <entry>Parameter foo was added. &version.trunk.after.53;</entry> </changelog> Also: - Add a few tools to doc.php.net that'll help see these - The main entity will link to [an updated] http://php.net/about.phpversions The aim is for these entities to be clear (mention 5.4/6.0), yet be easy to spot and find (we'll know when &version.trunk.after.53; was added). If these end up sticking around in translations, they'll still be correct (sort of) and again be easy to spot. Sound good? Thoughts? We should probably start doing this (or a version of) later this week. Regards, Philip
