-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13 Sep 2006, at 13:06, Miles Waller wrote:
Personally, I'm neutral on moving the requirement for CMF 2.1 to
Zope 2.10. Obviously we're not using any of those new features
yet, but it would be nice to enable their use by mandating 2.10.
CMF 2.2 will move the bar higher I'd wager.
I'd love to hear some kind of yay/nay for making Zope 2.10 the
required platform for CMF 2.1 from some other people like Tres,
Yvo, Florent etc.
One thing that would be good about this is that the CMFUid suite
could be deprecated in favour of an implementation based on zope3's
intids utility.
There was a discussion a while back about the future of that
package: http://mail.zope.org/pipermail/zope-cmf/2006-April/
024373.html
Yes, that would be a good thing, CMFUid isn't as "alive" as it was
hoped when the product was pushed into the CMF.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFFCQEbRAx5nvEhZLIRAugsAJ4pBxmqKlHdlMjiaiJSCVGLRsTIcQCfc7X2
DrrAhYmOiDB8CTbxITFDOhM=
=Nuwz
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
