On 31.10.2008 18:36 Uhr, Tres Seaver wrote:
In that case Plone will neither use 2.11 nor 2.12 but go straight for a
Zope 2.13 including Python 2.6. A major release every six month would be
desirable for us in that case. Right now I don't see anyone, who would
be using those releases. If those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 4, 2008, at 09:10 , Andreas Jung wrote:
In the meantime, we can acknowledge that 2.8 and 2.9 are
retired (no
future work except maybe important security fixes),
+1
and announce that
2.10 will be retired after the 2.12 release:
We
Jens Vagelpohl wrote:
On Nov 4, 2008, at 09:10 , Andreas Jung wrote:
In the meantime, we can acknowledge that 2.8 and 2.9 are
retired (no
future work except maybe important security fixes),
+1
and announce that
2.10 will be retired after the 2.12 release:
We have to care about
Summary of messages to the zope-tests list.
Period Mon Nov 3 12:00:00 2008 UTC to Tue Nov 4 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Mon Nov 3 21:10:28 EST
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 4, 2008, at 13:59 , Hanno Schlichting wrote:
If I'm not mistaken there was something about every release being
supported two years after its initial release in those discussions.
But time went on, we haven't sticked to a time-based
Jens Vagelpohl wrote:
On Nov 4, 2008, at 13:59 , Hanno Schlichting wrote:
If I'm not mistaken there was something about every release being
supported two years after its initial release in those discussions.
But time went on, we haven't sticked to a time-based release schedule
and those
Andreas Jung wrote:
On 04.11.2008 18:19 Uhr, Jens Vagelpohl wrote:
On Nov 4, 2008, at 13:59 , Hanno Schlichting wrote:
If I'm not mistaken there was something about every release being
supported two years after its initial release in those discussions.
But time went on, we haven't sticked
On 04.11.2008 18:41 Uhr, Hanno Schlichting wrote:
Andreas Jung wrote:
On 04.11.2008 18:19 Uhr, Jens Vagelpohl wrote:
On Nov 4, 2008, at 13:59 , Hanno Schlichting wrote:
If I'm not mistaken there was something about every release being
supported two years after its initial release in those
Squid seems to hang waiting for www.zope.org:8881 which currently breaks
buildouts/setuptools that sniff around zope.org
--
Christian Theune · [EMAIL PROTECTED]
gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889
Ross Patterson wrote at 2008-11-3 16:04 -0800:
...
If memory serves, a *functional* test fixture calls the Zope publisher
when a testbrowser request is made. The publisher opens a new
transaction, as it should.
Really?
When I wrote a functional test browser (years before zope3),
I emulated the
Dieter Maurer [EMAIL PROTECTED] writes:
Ross Patterson wrote at 2008-11-3 16:04 -0800:
...
If memory serves, a *functional* test fixture calls the Zope publisher
when a testbrowser request is made. The publisher opens a new
transaction, as it should.
Really?
When I wrote a functional test
11 matches
Mail list logo