-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On May 26, 2009, at 11:20 , Hanno Schlichting wrote: > Why doesn't that generate test failures? We are running nightly tests > testing CMF trunk with Zope 2.10, 2.11 and 2.12. OK, I found the problem. It was actually my fault. With the refactoring mania going on I specified the INameChooser interface in a ZCML declaration from its new location and did not realize it was moved there just recently. Now the tests pass again on Zope 2.10.8 and Zope 2.11.3 Sorry for the confusion! However, I'd still like to bring up the question of officially supported Zope releases for CMF 2.2.x. Speaking for me personally, I develop CMF trunk against Zope trunk (there's that nifty CMF.buildout package that makes this easy), and it's becoming a greater and greater effort to ensure backwards compatibility for all kinds of combinations. So, what do we want to support? jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkobuj4ACgkQRAx5nvEhZLJrywCgrKplXVtTqJZtS2r0uSSRywpz 198AnRijrq2DCNJF9grH6gBZhTD+ZH6b =4kmx -----END PGP SIGNATURE----- _______________________________________________ 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
