Re: [Framework-Team] Plone 3.5

Alec Mitchell wrote:

> I'd like to stand up for "my" release a little, since people seem to
> be implying it was some sort of expectations/compatibility disaster.
> Plone 2.5 introduced some new infrastructure and officially deprecated
> a number of old APIs, scripts and templates, but it maintained
> compatibility for all of those.  The only exception that I'm aware of
> is the introduction of PlonePAS, which theoretically offered API
> compatibility but failed in that regard with some 3rd-party add-ons.
> The scope of 2.5 was well defined, and highly constrained (in fact,
> Plone's official deprecation/compatibility policy was established as a
> part of the 2.5 release). The numbering jump may not have been ideal,
> but calling that release 3.0, when there were almost no outwardly
> visible changes (aside from deprecation warnings in your logs), would
> have also been a blunder, IMO.
> 
> If you want to pinpoint a release that broke expectations with regard
> to compatibility, Plone 2.1 is a far better example.  There were a
> huge number of incompatibilities and migration issues between 2.0 and
> 2.1.  The transition to ATCT alone was worth a major revision, never
> mind the numerous API and UI changes and configuration options
> removed/disabled (some of which were thankfully put back in place in
> 2.5).  If anything, Plone 2.5 began to establish a contract of major
> release compatibility that had been entirely destroyed with the 2.0 ->
> 2.1 transition.  Plone 2.5 wasn't perfect, but I find it hard to
> imagine it as the expectations nightmare people are portraying here.

This is my impression as well. 2.5 was not very exciting from a feature 
point of view, but it was an important release, and hardly a disaster.

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com