-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While profiling a basic Zope2 + Five application this afternoon against Zope 2.10.5, I discovered a huge performance bug in zope.security.management.newInteraction. It turns out that the bug had been fixed last summer, but only on the 3.4 branch and trunk for Zope3.
I therefore cut a standalone zope.security 3.3 branch (and 3.3.3 tag) for use in the Zope2 tree checkout. I would like to raise awareness that "important" bugfixes for Zope3 components may need to get more love than we have been giving them: in particular, we may need to be prepared to backport performance-, stability-, or security-critical fixes back to earlier versions than those which are currently under active development: the set of dependents is going to be increasing, and increasingly long-lived. As we move to finer-grained egg releases, keeping up with these backports should be simpler: only the package requiring the backport should need to be re-released. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHv3f1+gerLs4ltQ4RApxMAKCXHFCCnG7uPg3+TLETkUYMmgvrAQCfRDYP D4yHHXpprf8m2N/83tW7Sqk= =cjCw -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
