Hi Hannes,
Think about the online manual. In 2 years from now people should still
be able to read the upgrading guide and it should still make sense
without needing to hunt down random release announcements or outdated
NEWS files.
The upgrade which gets committed to php-src will be taken, word by
word, and ported to Docbook and made available at
http://php.net/migration53 (just like /migration52 and
/migration51..).
But this was actually an add-on after I put the initial 5.1 upgrading guide
together. A 200-line document became a 500-line document overnight, and
voila - nobody reads the thing.
Is this entirely necessary? (I can see a case for listing new classes in
the
global namespace.)
Unless you want duplicated work, one file to php-src and one for the docs,
yes.
I'd like to know why you can't just take release info from the release notes
for the manual. Duplicating the release notes seems a bit pointless.
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
