Re: Keep documentation for previous versions when updating it to reflect new behaviour and features
Wichert Akkerman <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Previously JoAnna Springsteen wrote: > > Part of the original reason for this email is that we had a small burp in > > our process. In Plone 3.3, the way versioning is displayed/implemented is > > completely different than it is in versions 3.0-3.2. > > This is the kind of stuff that the framework team shouldn't be doing. > tsk tsk. /me wags finger Yes and no. I agree this change changes behaviour in a way that people might not be expecting, which is not desirable in the 3.x series. There were two good reasons to still make it though: most packages keep the version numbers in setup.py, version.txt and metadata.xml in sync and will see no change, and Plone no longer mixes up profile and package versions which was a bug and was starting to confuse people. The distinction is important, and I felt that this was warranted to set things straight. Wichert. -- Wichert Akkerman <[email protected]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ------------------------------------------------------------------------------ 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