I agree with your analysis. Could you file a bug report in launchpad?
Bug now filed: https://bugs.launchpad.net/zope3/+bug/162166.
\malthe
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
Summary of messages to the zope-tests list.
Period Sun Nov 11 13:00:00 2007 UTC to Mon Nov 12 13:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Sun Nov 11 20:52:22 EST 2007
Hey,
On Nov 11, 2007 10:34 PM, Jim Fulton [EMAIL PROTECTED] wrote:
On Nov 11, 2007, at 2:06 AM, Martijn Faassen wrote:
[snip]
This breaks a fundamental assumption for releases. When I release
something, I expect it to work tomorrow, next month, and next year.
If you want this, then you
Hey,
On Nov 12, 2007 12:02 AM, Stephan Richter [EMAIL PROTECTED] wrote:
[snip]
Like Linux distributions, there will be a KGS for every Zope 3
release. I have already requested a new directory called zope-dev where new
feature releases can be tested.
Okay, I didn't understand that KGS is
I'm trying to get my head around the package versioning requirements.
It seems to me that we have the following requirements:
1. We need to be able to in a buildout say I want to use Zope version
3.4, thanks, and the buildout should then download the latest
versions of the relevant Zope packages
On Nov 11, 2007, at 6:34 PM, Stephan Richter wrote:
On Sunday 11 November 2007, Jim Fulton wrote:
This breaks a fundamental assumption for releases. When I release
something, I expect it to work tomorrow, next month, and next year.
If you want this, then you can't rely on the KGS. When
On Monday 12 November 2007, Jim Fulton wrote:
I thus propose that all packages in svn.zope.org should use a KGS
for testing,
because it is a fully public dependency graph. I am not sure
whether it
should be the latest stable KGS or the development KGS or whatever.
Time will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Winkler wrote:
On Sun, Nov 11, 2007 at 06:37:22PM -0500, Stephan Richter wrote:
Yes, everyone has to sign a contributor agreement, but you do not have to
become a Zope Foundation member.
I had the impression, from the recent ZF IRC chat,
On Mon, Nov 12, 2007 at 12:19:20PM -0500, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Winkler wrote:
On Sun, Nov 11, 2007 at 06:37:22PM -0500, Stephan Richter wrote:
Yes, everyone has to sign a contributor agreement, but you do not have to
become a Zope
On Monday 12 November 2007, Paul Winkler wrote:
I probably still have commit access from the pre-ZF days, but the
employer information I submitted has changed several times since then.
Now that I've started working for a more enlightened employer, I would
like to start checking in bugfixes
Stephan Richter wrote:
The easiest way to do this is to add the following line to the buildout
section of the package's `buildout.cfg` file:
index = http://download.zope.org/zope3.4
(I know you know that Jim; it is for the benefit of people reading this
mail. ;-)
I've been trying to follow
On Nov 12, 2007, at 2:00 PM, Paul Winkler wrote:
On Mon, Nov 12, 2007 at 12:19:20PM -0500, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Winkler wrote:
On Sun, Nov 11, 2007 at 06:37:22PM -0500, Stephan Richter wrote:
Yes, everyone has to sign a contributor agreement,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Stephan Richter wrote:
The easiest way to do this is to add the following line to the buildout
section of the package's `buildout.cfg` file:
index = http://download.zope.org/zope3.4
(I know you know that Jim; it is for the
13 matches
Mail list logo
