Hi.
On Sun, Oct 17, 2010 at 4:10 PM, Hanno Schlichting ha...@hannosch.eu wrote:
With the release of both a final ZODB 3.10 and the ZTK 1.0, we are
good to go on a release candidate for Zope 2.13.
There's currently two bugs I consider blockers for the release candidate:
- zopectl start -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/28/10 12:29 , Hanno Schlichting wrote:
- zopectl start - doen't work (https://bugs.launchpad.net/zope2/+bug/628448)
- Zope2 egg is not available in index
(https://bugs.launchpad.net/zope2/+bug/653546)
Both of these have been resolved now.
On Thu, Oct 28, 2010 at 1:32 PM, Jens Vagelpohl j...@dataflake.org wrote:
On 10/28/10 12:29 , Hanno Schlichting wrote:
Both of these have been resolved now. The index problem is waiting for
a Apache config reload on download.zope.org.
I reloaded it. What did you change?
I explained it to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/2010 10:10 AM, Hanno Schlichting wrote:
Hi.
With the release of both a final ZODB 3.10 and the ZTK 1.0, we are
good to go on a release candidate for Zope 2.13.
There's currently two bugs I consider blockers for the release candidate:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/2010 10:10 AM, Hanno Schlichting wrote:
Hi.
With the release of both a final ZODB 3.10 and the ZTK 1.0, we are
good to go on a release candidate for Zope 2.13.
There's currently two bugs I consider blockers for the release candidate:
On 10/18/10 1:20 PM, Tres Seaver wrote:
On 10/17/2010 10:10 AM, Hanno Schlichting wrote:
Hi.
With the release of both a final ZODB 3.10 and the ZTK 1.0, we are
good to go on a release candidate for Zope 2.13.
There's currently two bugs I consider blockers for the release
candidate:
Hi.
With the release of both a final ZODB 3.10 and the ZTK 1.0, we are
good to go on a release candidate for Zope 2.13.
There's currently two bugs I consider blockers for the release candidate:
- zopectl start - doen't work (https://bugs.launchpad.net/zope2/+bug/628448)
- Zope2 egg is not