-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 4 Jun 2006, at 16:04, Rocky Burt wrote:
Anyhow, I've included a patch that demonstrates what would need to be
done including some extra test logic that fails before my changes
and of
course passes afterwards.
What do you all think? Something we can include in time for CMF1.6.1
beta2 ?
There won't be any beta2 due to the short notice I had for the
imminent Plone 2.5 release, I was glad I got in a single one-week beta.
- -1 on including it in 1.6.1
I'm also not very keen on putting it in 1.6.2.
As Yvo and Tres already implied, Plone is the single reason for
having the CMF 1.6 release. It would have been better if ideas like
these had come up earlier and not at the very last minute. I mean, we
all knew when Plone 2.5 was going to land, they have a roadmap
document. Furthermore, I'm of Tres' opinion when it comes to the
actual need of such a patch. Personally I'd move that up to the next
Plone feature release and CMF 2.1 (currently trunk).
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEgycFRAx5nvEhZLIRAnpVAJ99pQGkXQwK+jb8CS4dIoPxjXUu6QCeLcC9
kTdeLx2QNBQjQ+NJufRKlSM=
=QDF6
-----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
