-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On Sun, Dec 27, 2009 at 8:31 PM, Jens Vagelpohl wrote:
>> Please keep release scheduling in mind. I had announced a release date
>> for CMF 2.2.0-final about a week from now. Andreas cannot possible throw
>> out Zope 2 2.12.
On Sun, Dec 27, 2009 at 8:31 PM, Jens Vagelpohl wrote:
> Please keep release scheduling in mind. I had announced a release date
> for CMF 2.2.0-final about a week from now. Andreas cannot possible throw
> out Zope 2 2.12.3-final by that time. We would need to postpone CMF
> 2.2.0-final for any of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On a related note, if I'm going to backport the five.formlib
> extraction to 2.12, it would it be ok to depend on a 2.12.3 release
> for CMF 2.2 with this stuff in it, right?
Please keep release scheduling in mind. I had ann
On Sun, Dec 27, 2009 at 5:45 PM, yuppie wrote:
> Hanno Schlichting wrote:
>> Just to make this explicit: CMF trunk should continue to run with Zope
>> 2.12 and not only with 2.13, correct?
>
> Yes. At least until there is an explicit decision to drop 2.12
> compatibility. So far I can't see a good
Hi!
Hanno Schlichting wrote:
> Just to make this explicit: CMF trunk should continue to run with Zope
> 2.12 and not only with 2.13, correct?
Yes. At least until there is an explicit decision to drop 2.12
compatibility. So far I can't see a good reason for dropping BBB.
> If so, I'll add a sec
Hi.
On Sat, Dec 26, 2009 at 6:25 PM, Yvo Schubbe wrote:
> Log message for revision 107108:
> - fixed Zope 2.12 compatibility
Just to make this explicit: CMF trunk should continue to run with Zope
2.12 and not only with 2.13, correct? If so, I'll add a second test
runner to the buildout, so it's
