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
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
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 11, 2007 8:06 AM, Martijn Faassen [EMAIL PROTECTED] wrote:
I therefore still believe that version dependency information should
move out of external indexes and into packages.
This is at least the intuitive place for this information. My
application requires Grok 0.11, which requires
Previously Martijn Faassen wrote:
People have been saying that since Linux distributions use external
indexes, we should too, as we are dealing with the same problem as Linux
distributions. While the problem is similar, I think the nature of
development makes our problems, and therefore our
On Nov 11, 2007, at 2:06 AM, Martijn Faassen wrote:
Hi there,
I've been doing some more thinking about external version indexes
(like Grok's versions.cfg on a URL, and like KGS) and why they
won't solve all our problems. I have a new way to express it, so
let me try it out on you all.
On Sunday 11 November 2007, Lennart Regebro wrote:
On Nov 11, 2007 8:06 AM, Martijn Faassen [EMAIL PROTECTED] wrote:
I therefore still believe that version dependency information should
move out of external indexes and into packages.
This is at least the intuitive place for this
On Nov 11, 2007, at 6:11 PM, Stephan Richter wrote:
On Sunday 11 November 2007, Lennart Regebro wrote:
On Nov 11, 2007 8:06 AM, Martijn Faassen [EMAIL PROTECTED]
wrote:
I therefore still believe that version dependency information should
move out of external indexes and into packages.
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 releasing our
applications, we don't rely on a KGS.
Hi there,
I've been doing some more thinking about external version indexes (like
Grok's versions.cfg on a URL, and like KGS) and why they won't solve all
our problems. I have a new way to express it, so let me try it out on
you all.
What KGS solves is that it allows the ongoing development
12 matches
Mail list logo
