-----BEGIN PGP SIGNED MESSAGE-----
On May 26, 2009, at 10:21 , Wichert Akkerman wrote:
> Previously Jens Vagelpohl wrote:
>> The CMF eggs, even on trunk, still advertise compatibility with Zope
>> 2.10. I believe we had agreed to target Zope 2.12 with trunk - please
>> correct me if that's wrong. If we do want Zope 2.12 I would like to
>> through before the first CMF 2.2 beta and do the following:
>> - adjust all setup.py files to show the Zope2 egg as dependency,
>> which will imply the "Zope2 >= 2.12dev" dependency
>> - go through and delete all BBB code for Zope versions earlier than
>> If anyone thinks that's a bad idea please speak up.
> I think we are targetting Plone 4 at CMF 2.2 and Zope 2.11 at the
> moment, so that would be bad for us.
I'm guessing you are not aware that there already is a hard dependency
in CMFDefault. In essence, I would not be setting a new policy, I
would document the current situation.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests