> just some quick points:
>
> - when you do documentation, even for your own extension,
>you usually do not know in advance which version you stuff
>will be in
>
>it is hard to decide where to set the tag in the doc branch
>unless you have your code and docs really in sync
>
>i
Colin Viebrock wrote:
> Can the documentation folks use release tags like the dev folks do? For
> instance, when PHP 4.2.0 is release, make a PHP_4_2_0 branch in CVS for the
> docs. [...]
just some quick points:
- when you do documentation, even for your own extension,
you usually do not kno
> In an IRC chat with Derrick, it was brought up that getting translators to
> work with CVS branches could possibly make my idea undoable (i.e., it's
> asking too much of people to learn how to use branches properly).
> Personally, I disagree, but that can be discussed here as well.
An itelligen
> Something like this problem was discussed on our meeting at Stuttgart.
> We came up with the idea of including a "Changelog" on all function
> pages where it is needed. We can't freeze the docs for specific PHP
> versions as we often discover undocumented features let's say, from
> PHP 4.0.0...
> It seems to be that a lot of the time, the documentation on the website is
> out of step with the latest release of PHP. In almost all of these cases,
> PHP is at version X, and the online docs are describing version X+1, or
the
> CVS version.
>
> Case in point: the DOMXML extension is now much
I'm not really involved in the documentation side of things, so take what I
say with a grain of salt.
It seems to be that a lot of the time, the documentation on the website is
out of step with the latest release of PHP. In almost all of these cases,
PHP is at version X, and the online docs are
