Yvo,
The following checkin on the 1.6 branch, which looks like a pure
cleanup item, completely breaks Plone 2.1 and up on CMF 1.6. I assume
that was not the intention.
http://svn.zope.org/CMF/branches/1.6/CMFCore/TypesTool.py?
rev=40364r1=40360r2=40364
I'm in the specific situation
Alec Mitchell wrote:
to start using it immediately or risk strange breakages. Maintaining
product compatibility between versions of CMF/Plone will become nearly
impossible.
I'm sorry, I really couldn't resist this...
And that differs from other Plone releases how exactly? ;-)
Chris
--
I'd like to have some clarifications from the Plone team about what
they expect to do w.r.t. events in CMF 1.6.
I see two possibilities:
1. you guys are prepared to do the work needed for Plone products to
use super() in manage_afterAdd co, in which case I can merge my
branch into CMF 1.6
On Wednesday 16 November 2005 01:41 pm, Florent Guillaume wrote:
I'd like to have some clarifications from the Plone team about what
they expect to do w.r.t. events in CMF 1.6.
I see two possibilities:
1. you guys are prepared to do the work needed for Plone products to
use super() in
yuppie wrote:
I would not like to do this work on different branches, but if
GenericSetup is a SVN external or if someone else does the merging I'm
fine with creating the 1.6 branch earlier. Anyway I don't think 1.6 can
be released before 2.0.
okay, i've created a CMF-1.6 branch that has
