Previously Jens Vagelpohl wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > 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 go > 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 > 2.12 > > 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. Wichert. -- Wichert Akkerman <wich...@wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests