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

On Mon, Apr 20, 2009 at 8:41 AM, Wichert Akkerman <[email protected]> wrote:
> 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.

As far as I've understood, Darci was talking about:

    * Versioning (Plone v3.0 - Plone v3.2):
http://plone.org/documentation/manual/plone-3-user-manual/managing-content/versioning-plone-v3.0-plone-v3.2
    * Versioning (Plone v3.3+) :
http://plone.org/documentation/manual/plone-3-user-manual/managing-content/versioning-plone-v3.3

not about the changes in the QuickInstaller.

-- israel

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