-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jens Vagelpohl wrote: > > On 19 Dec 2006, at 13:00, CMF Tests Summarizer wrote: > >>> Summary of messages to the cmf-tests list. >>> Period Mon Dec 18 12:00:00 2006 UTC to Tue Dec 19 12:00:00 2006 UTC. >>> There were 9 messages: 9 from CMF Unit Tests. >>> >>> >>> Test failures >>> ------------- >>> >>> Subject: FAILED (failures=3) : CMF-trunk Zope-trunk Python-2.4.4 : >>> Linux >>> From: CMF Unit Tests >>> Date: Mon Dec 18 21:54:27 EST 2006 >>> URL: http://mail.zope.org/pipermail/cmf-tests/2006-December/ >>> 003568.html > > @Tres: These failures are due to the still-existing DateTime changes > on the Zope trunk which you reverted on all other affected branches. > Was not reverting them an oversight or planned?
I was leaving them on the trunk so that the original author could "fix" them by adding BBB. Having CMF broken against the Zope trunk is OK with me, at least for a bit. On the release branches, I felt safer in reverting them, because the new semantics were breaking CMF. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v184.108.40.206 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFh/pf+gerLs4ltQ4RArTCAJ9jMAH8xDHhDFWTY4mLArb2g/PYIQCggHOL hM2u+XArDqIk0X7TCArHrOM= =0a6d -----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