Hi!
I'd like to make Zope 2.10 required for CMF trunk (2.1). This was
discussed before in this thread:
http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html
In my sandbox I removed the Zope 2.9 backwards compatibility code and
got rid of all deprecation warnings. If there are
Previously yuppie wrote:
I'd like to make Zope 2.10 required for CMF trunk (2.1). This was
discussed before in this thread:
http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html
+1 here. Plone 3.0 has the same Zope requirement.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1 Nov 2006, at 04:27, yuppie wrote:
Hi!
I'd like to make Zope 2.10 required for CMF trunk (2.1). This was
discussed before in this thread:
http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html
In my sandbox I removed the Zope
Am 01.11.2006 um 14:06 schrieb Jens Vagelpohl:
I'd like to make Zope 2.10 required for CMF trunk (2.1). This was
discussed before in this thread:
http://mail.zope.org/pipermail/zope-cmf/2006-September/024813.html
In my sandbox I removed the Zope 2.9 backwards compatibility code
and got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think trying to come up with a list of applications that will
break is utopian. We're not talking locked-down walled garden
here where the vendor has control over what the customer runs. We
cannot anticipate what will break, apart from very