On Nov 19, 2007, at 2:17 AM, Stephan Richter wrote:
On Sunday 18 November 2007, Chris McDonough wrote:
I disagree. This is not what this means to me. I think a KGS can
receive bug
fix releases, which the Zope 3.4 KGS does. However, no new feature
releases
are allowed.
In the Linux world, thes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan Richter wrote:
> On Sunday 18 November 2007, Chris McDonough wrote:
>>> 4. A new "minimal/" folder now contains an index just of the
>>> controlled
>>> packages. This minimal index can be used by compoze as one
>>> contributing
>>> index. (I ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris McDonough wrote:
> On Nov 18, 2007, at 7:52 PM, Stephan Richter wrote:
>
>> On Sunday 18 November 2007, Chris McDonough wrote:
4. A new "minimal/" folder now contains an index just of the
controlled
packages. This minimal index ca
On Nov 19, 2007, at 9:54 AM, Tres Seaver wrote:
It's a limitation of buildout, perhaps. It is possible to use
setuptools with multiple indexes: 'compoze' allows spelling multiple
'-index-url' items on the command line. E.g.::
I'm curious what API you're using.
buildout uses setuptools.pack
On Nov 19, 2007, at 1:26 PM, Dieter Maurer wrote:
Chris McDonough wrote at 2007-11-18 16:50 -0500:
...
Note that if the KGS really wants to be a KGS (literally "known
good",
it's a matter of semantics, not of technology):
- An invariant must be met that only one version of each package
sho
On Nov 19, 2007, at 2:52 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Nov 19, 2007, at 9:54 AM, Tres Seaver wrote:
It's a limitation of buildout, perhaps. It is possible to use
setuptools with multiple indexes: 'compoze' allows spelling
multip
On Monday 19 November 2007, Chris McDonough wrote:
> Now we just need to define what a "release"
> is ;-)
Yes, I thought about this a little bit this weekend and I would love to see
some discussion. For example, I do not think it will be necessary to create a
new release for every change in th
Hi,
I am currently writing a doctest for one of my persistent classes. It's
purpose is to check, if object modifications, e.g. through methods, are
really persistent, however, my objects are magically remembered, therefore I
cannot properly test them.
My doctest looks like this:
>>> from ZODB
Hi Dieter
> Betreff: Re: [Zope-dev] KGS Site Updated
>
> Chris McDonough wrote at 2007-11-18 16:50 -0500:
> > ...
> >Note that if the KGS really wants to be a KGS (literally
> "known good",
> >it's a matter of semantics, not of technology):
> >
> >- An invariant must be met that only one versio
On Sun, 18 Nov 2007 23:17:53 -0800, Stephan Richter
<[EMAIL PROTECTED]> wrote:
So if you go to http://download.zope.org/zope3.4/intro.html into the
sub-section "Version 3.4.0b2" you see a bunch of links.
Just a minor observation, nowhere on that page is it explained what KGS
means. :)
--
10 matches
Mail list logo
