Re: Keep documentation for previous versions when updating it to reflect new behaviour and features

Veda Williams wrote:
> The goal is to release documentation that is older into the broader
> "knowledgebase" space. And Joanna's right, we won't be removing any
> documentation, we're just going to flush it out of the core documentation
> area.
> 
> Since we're moving toward a manual-based system, it makes sense to create
> them in a way that we can flag them as being specific to a given major
> version of Plone. 
> 
> Within a given version, we can still indicate where something applies to 3.3
> or 3.4 within the 3.x manual, since there will obviously be incremental
> change, but I don't think we should have new manuals for minor versions of
> Plone, just from the maintenance standpoint.

Once we have the manual in place - and it looks like we come a long way
already - I'm not sure it would produce much of a maintenance overhead
to even release the manual for minor versions.

Just look at, e.g., http://www.python.org/doc/versions/
Most of the stuff there is identical across versions but as Dylan
points out this is much easier to deal with from a user's point
of view.

Raphael

> 
> - Veda
>


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p