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

Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]>
Newsgroups gmane.comp.web.zope.plone.documentation
Message-ID <[email protected]>
On 19/04/2009, at 7:23 PM, Israel Saeta Pérez wrote:

> I'd prefer to keep it as is now, since the aren't so many changes
> between some version of Plone 3 and the following one, and having to
> "duplicate" all docs when only a paragraph is added to some docs isn't
> very efficient IMO. A more pragmatic approach is specifying that

not very efficient in terms of diskspace or time or something else?


> something is only valid since Plone X.Y next to that paragraph, and
> that's why we are doing for now. A bit more confusing, I must agree,
> but more pragmatic too.

so you're reading along and constantly have to monitor the version  
number next to each paragraph to find out if the paragraph applies to  
the one and only one version you are interested in?



------------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.