These should all, along with any other inline version information, go
into changelogs.
These changelogs are a goldmine when looking through a application
that has been with us throughout time and received incremental
upgrades as time goes.
Lets not fuckover the people that has been with us this long.
Sure. I'll start fixing it.
[...]
We could resurrect overload and domxml and export into .html page like
php3.php? Is that what they are asking for?
I think that providing compressed/online snapshot of specified revision
somewhere on doc.php.net would be more convenient and even easier to prepare
for us. Opinion based on post written by Chris Wright in this topic.
No. Thats a major annoying maintenance headache.
We've got http://php.net/manual/php3.php (its thinner then I remembered?)
Lets add the PHP4 specifics (oop4, dotnet, sw, domxml, ...) to php4.php there.
I still consider this approach more useful for users and simpler for us. What's the problem in hosting built (downloadable) versions of specified revision somewhere? Traffic? I'm proposing to build them only once, not regularly. After that, anyone who may need manual containing info about PHP 4 will be able to download complete documentation, not two documents incredibly hard to understand because they would refer each other constantly.
-Hannes
Regards,
Maciej.