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

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.

- Veda


On 4/19/09 7:55 AM, "JoAnna Springsteen" <[email protected]> wrote:

> When someone creates a doc on plone.org, there is a place to select
> which version of Plone this doc applies to.
> I believe Veda and SteveM have plans of doing a reorganization of how
> information is presented on the Documentation landing page. Because we
> already capture this data, all we have to do is clearly link to it.
> 
> As for what we keep...We still have docs that support the 2.1 release.
> We keep these. We don't delete. Most of them have been marked as
> obsolete or hidden. But we don't delete stuff. You should still find
> 2.5 documentation out there on plone.org, but it's not as prevalent as
> the 3.x docs. This is mainly because we have had a more focused effort
> on documenting 3.x than we had for 2.5. Now, we don't actively write
> 2.5 docs and we haven't for awhile. But the info is still around for
> those that need it.
> 
> As for resources, well you know the story. The doc team is always
> strapped for resources so no, we don't have the capacity to support
> multiple versions. It's not something we can even as the team to do
> because we just don't have enough regular volunteers that contribute
> to writing docs. But we will keep the 2.5 docs we do have. I don't
> anticipate us making them hidden anytime soon as so many people still
> do use 2.5...we just don't focus on writing anything new for that
> version.
> 
> J.
> 
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> Plone-docs mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-docs


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