I am proposing to have ONLY two versions:
. the current development version
. the last released version
i.e. when a new release is ready, the previous releases
documentation is removed and the new documentation takes
its place.
So for example:
{1} http://j.a.org/commons/project/index.html
{2} http://j.a.org/commons/project/development/index.html
would be the only two documentation locations. {2} would
be linked in such a way that it is obvious that it is the
development site.
The reason I mentioned this is so patches to documentation can
be actively reviewed from j.a.org without disturbing the release
doc.
-John K
On Tue, 2002-11-12 at 17:17, Henri Yandell wrote:
> > On Tue, 2002-11-12 at 12:11, John Keyes wrote:
> > > I think there should be two copies of a projects documentation
> > > on the Jakarta site. One is the release copy i.e. the documentation
> > > for the last release, the other is the actual project homepage
> > > where the latest documentation is maintained. Do any projects
> > > do anything like this?
>
> Tomcat do this. 5 versions on the current site, although they also
> maintain multiple branches which is quite a developer overhead in my
> opinion and not something a small commons project could handle on its own.
>
> Hen
>
>
> --
> To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
--
John Keyes <[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
