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

Raphael Ritz wrote:
> Hanno Schlichting wrote:
> 
> [..]
> 
>> To my best knowledge the version policy I proposed met the boards favor,
>> which means at this point Plone 3.2 is the only supported release.
>> Support for Plone 2.5 of any kind has ended with the release of Plone
>> 3.1 about a year ago.
> 
> While I think that's correct I'd prefer us to be pragmatic
> here. From what I know there are still many sites out there
> that are on Plone 2.5.x (and some even older than that).
> 
> When it comes to documentation I would not purposefully remove
> the old stuff per default but simply mark it as such, e.g., like
> Dylan suggested. I don't see any harm in keeping old documentation
> around as long as we do it in such a way that people don't get
> confused.
> 
> So for me, the question boils down to: how to best avoid potential
> confusion without simply removing the old stuff?

+1

2.5 is not supported anymore in terms of maintenance updates of the
codebase (2.5.5 was released in Dec 2007).

If the documentation team has the resources to maintain the
documentation for multiple versions, that is a decision the team ought
to do.

Hanno


------------------------------------------------------------------------------
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