Re: [Framework-Team] Plone 3.5

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.

> My worry here is that catching up will mean a repeat of 2.5. 

What does that mean?

> Not to mention if we are changing this much stuff on a platform level that it
> won't get documented. The framework team would have to be responsible
> for documenting these changes as the documentation team just does not
> have the man power. Sure, we made the 3.3 release w/ documentation and
> that was relatively small stuff. If you go for a bigger release under
> the 3.x series we're going to end up back where we started....New
> technologies and no documentation. This will further the idea that
> being a Plone developer is only for elite code jockeys. That's not
> really something we want to reinforce, is it?

This sounds like a false dichotomy to me, and basically an argument for 
doing *no* innovation, which is surely not what you meant.

The framework team wouldn't need to document anything. PLIP implementers 
would be asked to provide documentation. And many of the features are 
end-user things that probably the docs team could help with.

> I gotta tell ya, this idea makes me really really nervous. I thought
> the whole point of 3.x was to be stable and not repeat past mistakes?
> I'm all for getting closer to 4.x but we need to do it in bite sized
> steps, not all at once.

I think you may have missed the point here...

Going straight to 4.0/trunk would be all-at-once. The 3.5 proposal is 
about creating a mid-point between what we have now (3.x) and that 
(4.0), that gives us some of the platform changes that will be necessary 
going forward, some of the features that we can deliver now rather than 
waiting 12-18 months, but not all the game-changing stuff like Deco or 
making Archetypes optional.

... so pretty much what you asked for. :)

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