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 2:01 AM, Israel Saeta Pérez wrote: > On Sat, Apr 18, 2009 at 5:40 PM, Hanno Schlichting <[email protected] > > wrote: >> Israel Saeta Pérez wrote: >>> If I'm not wrong, Plone 2.5 is still supported so anything from >>> 2.5 to >>> 3.x should be kept. >> >> /me looks at Steve >> >> I haven't seen any final official stance at this after the Board >> meeting >> on January 8, 2009: >> >> Follow up on Version Support Policy >> >> Steve will prominently post policy arrived at in PF membership >> discussion >> >> >> 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. > > Does that mean that there won't be security patches for Plone<3.2? > What does supported mean in this context? Just documentation support? Not sure about policies etc in my opinion one the least confusing ways of doing it is to keep copies of official manuals in folders marked with the version number... like python does http://www.python.org/doc/2.4.4/lib/lib.html Then the documentation reader *always* knows at a glance they are/ aren't reading the documentation for the version they want. Just my $0.02AUD Does that work with what the board and/or documentation direction is? ------------------------------------------------------------------------------ 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