> -----Original Message-----
> From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]]
>
> My attitude is this... The purpose of the website is to
> engage people in
> the project... The purpose of the documentation in the
> release build is
> to document that release. So the website should be bleeding
> edge...the
> release docs should match the release.
But why not have the latest version as well as the latest stable
version? The project has the latest version of the software
(the nightly builds and/or the CVS repository) as well as
released versions.
Admittedly, that's not 100% parallel (since the releases include
documentation (as they should). However, why not also provide the
released-version documentation on line? There could be a link to
the 1.4 documentation and a sibling link to the beta 1.5 documentation.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
