Am 28.09.2011, 17:20 Uhr, schrieb Laurence Rowe <l...@lrowe.co.uk>:
> Plone tends to wait for CMF to stabilise before thinking of moving to
> a new version. At least when I last looked around a year ago (after
> adding some workflow pluggability into CMF) CMF trunk broke far too
> much in Plone to consider it for a minor revision.
Fair enough, although CMF releases tend to be very stable.
> Hopefully someone
All too often that someone tends to be yuppie...
> will put the effort in to port Plone to CMF 2.3 in time for Plone 5.
> It's certainly true that CMF is a smaller part of Plone than it used
> to be, that's down to the introduction of the component architecture
> so new features tend to be built on that instead.
FWIW I just ran the tests for CMFDefault with Chameleon. Seems to breaks
in the doctests due to the way i18n is handled.
Clark Consulting & Research
Zope-CMF maillist - Zope-CMF@zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests