There is probably "not enough" overlap between the internals and documentation team... Some guys here can add documentation on most of the functions is proper prototypes are in the source code, and it is understandable what the function does. Otherwise it is common practice that an extension writer documents the functions he added, and the doc team refines it, fits it into the build system, adds interlinks, fixes errors, mispelling, adds missing functions, etc. This was the case for example lately with the tidy extension (or the mysqli extension).
I agree with that 100%, however when it comes to the question I raised, how do we document the version for php as there is beta's and the such do we start documenting now etc, shouldn't this be a doc team problem? I'm pretty new to this list so I'm not sure how things work etc but that's just the way I view it, however if things are done differently please feel free to put me in my place
There are already quite some functions in the doc source available only in PHP 5. Every function has a compatibilty part on the documentation page, which will include PHP 5 (currently only some text is displayed that the function is not available in a production version of PHP)... So feel free to add function documentation, the appropriate version numbers will get in there automatically.
Goba
