Re: [Framework-Team] Plone 3.5

Raphael Ritz wrote:
> [Do we really need to discuss this on three lists?]

Think of the fun and excitement of all those new emails in your inbox... 
(no, we don't, but it's too late now)

> Martin Aspeli wrote:
>> JoAnna Springsteen wrote:
>>>> The idea is also to catch up with our platforms (Zope 2, Zope 3, CMF) as
>>>> we're starting to look a bit out of date on Zope 2.10 + Zope 3.3 + CMF 2.1.
>>> What's the significance of 3.5? Why can't this catch up be done in
>>> increments? 3.4 then 3.5 then 3.6?
>> Because upgrading Zope versions and some of the other changes are too 
>> big for the Plone 3.x stability promise.
> 
> Do we know that for sure already?
> Do we know how far we could get with some temporary
> module aliases to take care of stuff that has been
> moved around?

This is a good point. But it feels risky nonetheless. It was definitely 
something we held up as an example of something we wouldn't do in a 
minor release.

It almost certainly will break some third party add-ons, but hopefully 
not any well-behaved ones. I guess only time will tell.

Some of the '2009' features also involve changing templates in a way 
that could cause some breakage to particular customisations as well.

> As I understand the current discussion the general idea
> is most welcome. People are concerned of staying in line
> with our long-term promises and it seems to me that this
> almost exclusively boils down to a naming issue.

Yep. I think this is a healthy debate, and I'm personally only +0.25 on 
the 3.5 name.

I'm a bit worried that in the past, we've tried to accompany the .0 
releases with a bit more fanfare, e.g. on CMSWatch, Digg, and so on. 
This release probably wouldn't warrant that type of release management. 
But that's not to say we can't tell a good story around a less ambitious 
4.0 release and talk up a 5.0 later.

> Frankly speaking I would have no problem calling the proposed
> intermediate release Plone 4 and not to assign a version number
> to current trunk at all. AFAICS the current co-notation of
> Plone 4 being the all-new, all-shiny next generation of Plone
> is merely a project internal that we can redefine without
> much of a problem but doing it the other way around because
> we consider sneaking in a major release before the next major
> release that some got used to think of being Plone 4
> carries the risk of creating confusion and distrust where we
> can't control it.

That's a really long sentence, but I think I agree... :)

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