Re: Plone 3.5

[Raphael Ritz]

Hanno Schlichting wrote:

> Hi.
>
> While everyone is waiting for Plone 4 and its rather long timeline, some
> people have been thinking about how to bridge the gap between the
> current stable 3.x releases and the future.
>
> The general idea that seems to have met some consensus is to go for a
> Plone 3.5 release up next. We'd skip any 3.4 release and go for a 3.5
> that is similar in spirit to the Plone 2.5 release. It tries to both
> refresh some of our technical underpinnings in addition to some more
> intrusive feature changes we didn't allow ourselves in the 3.x series so
> far.

While I like the idea in general I would be very careful not to break
our promise of Plone 3.x being stable, maintained, backwards compatible,
not breaking 3rd-party add-ons etc. until Plone 4 is out for a while.

Just for the record: we (the Plone 3 framework team) even got some
critic from the doc team for allowing

   http://plone.org/products/plone/roadmap/243

into Plone 3.3 as this had somewhat of an impact on the
forthcoming manual. (not to mention all the printed books
that appeared recently and that are going to appear soon)

After quickly browsing through Hanno's list I don't see a
reason to break our pattern and to call this 3.5. At first
glance it seems perfectly feasible to me to introduce at least
most of the changes proposed here in Plone 3.4, 3.5, 3.6.

Having said that I'm not so sure this should be handled by the
Plone 4 FWT alone. Regarding the release manager on the other
hand I have nothing but a warm welcome and the best wishes for
Eric! Glad to see you getting more involved.

Of course I would have specific comments on some of those changes
but this is not the place and time to do into the details I guess.

Just my 2 cents,

        Raphael


------------------------------------------------------------------------------
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
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs

[Carsten Senger-3]

Hanno Schlichting schrieb:

> While everyone is waiting for Plone 4 and its rather long timeline, some
> people have been thinking about how to bridge the gap between the
> current stable 3.x releases and the future.
>
> The general idea that seems to have met some consensus is to go for a
> Plone 3.5 release up next. We'd skip any 3.4 release and go for a 3.5
> that is similar in spirit to the Plone 2.5 release. It tries to both
> refresh some of our technical underpinnings in addition to some more
> intrusive feature changes we didn't allow ourselves in the 3.x series so
> far.

[...]

> This is only a proposal that needs community feedback and encouragement
> at this point to make it into an official roadmap. The next steps are to
> have an open discussion about this for the next one to two weeks. If it
> meets general favor, we will appoint the new/old framework team and let
> them recommend a release manager to the Foundation board for official
> nomination.

Improving Plone and cleaning up things is always a good thing. But a 3.5
major release will break the users expectations to have a stable
backward compatible 3.x release cycle. It's also confusing to name a
major version x.5 with all the consequences like incompatible 3.x
Add-Ons. The naming of Plone 2.5 was a rather unfortunate thing. The
proper naming for a backward incompatible release should be 4.0. I think
nobody wants a short living 4.0 release and rename the current Plone 4
to Plone 5.

I'm in favour to put as much changes into a 3.4 that are backward
compatible. I think it's ok to change some defaults for new Sites that
can be easily changed by an administrator like TinyMCE/optional
packages/Additional Roles that can. Thus I don't now what consequences
this would have for our documentation team.
Changes that bring other than really minor incompatibilities for 3.x
add-ons are a no-go for a 3.x release imho.


..Carsten


------------------------------------------------------------------------------
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
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs

[vedaw]

Hello,

FWIW, Darci Hanning is rewriting the chapter for Practical Plone 3 to
address this change.

Cheers,

- Veda


On 5/5/09 5:21 AM, "Raphael Ritz" <[hidden email]> wrote:

>
> Just for the record: we (the Plone 3 framework team) even got some
> critic from the doc team for allowing
>
>    http://plone.org/products/plone/roadmap/243
>
> into Plone 3.3 as this had somewhat of an impact on the
> forthcoming manual. (not to mention all the printed books
> that appeared recently and that are going to appear soon)
>

------------------------------------------------------------------------------
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
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs