On 10 Nov 2007, at 14:06 , Tres Seaver wrote:
If we have software which can generate the pacakge index at a URL
for a
KGS, then it could certainly generate a 'version.cfg' as well, to
support buildout.
We already do. Stephan's zope.release does that already. The file is
actually available t
On Friday 09 November 2007, Tres Seaver wrote:
> A KGS needs to have the following properties:
>
> - The "generation zero" of any KGS is an empty set of revisions.
Yes, luckily we are far beyond that point.
> - By default, any revision N of a KGS starts out as a "draft" version
>which is an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
> Tres Seaver wrote:
>> A KGS needs to have the following properties:
>>
>> - The "generation zero" of any KGS is an empty set of revisions.
>>
>> - By default, any revision N of a KGS starts out as a "draft" version
On Nov 10, 2007 1:06 PM, Stephan Richter <[EMAIL PROTECTED]> wrote:
> Right, I am already correctly branching the zope.release package. It contains
> the controlled-packages.cfg. Using the scripts in zope.release, it is trivial
> to render versions.cfg; I mean as in: ./bin/generate-versions
>
> I h
On Saturday 10 November 2007, Lennart Regebro wrote:
> On Nov 10, 2007 12:52 PM, Stephan Richter <[EMAIL PROTECTED]>
wrote:
> > While I personally do not think that this is a good idea, I am open to
> > the suggestion to fix the KGS versions for a particular Zope 3.4 release.
> > For example, inst
On Nov 10, 2007 12:52 PM, Stephan Richter <[EMAIL PROTECTED]> wrote:
> While I personally do not think that this is a good idea, I am open to the
> suggestion to fix the KGS versions for a particular Zope 3.4 release. For
> example, instead of having just a versions.cfg, we can expand the scripts t
On Friday 09 November 2007, Martijn Faassen wrote:
> Roger Ineichen wrote:
> > Hi Tres
> >
> >> Whoever released those two eggs (the '.dev-r#' ones) need
> >> to release "real" updated packages, and then grok 0.11.1
> >> should be released using them.
> >>
> >> DEATH TO FAUX PACKAGES!
> >
> > A
On Nov 10, 2007 10:02 AM, Philipp von Weitershausen
<[EMAIL PROTECTED]> wrote:
> I sympathize with this thinking, but as far as I understood Jim and
> Stephan last night, there seems to be the goal to make a KGS for a whole
> stable release branch, e.g. "Zope3.4", and keep on adding bugfix
> releas
Tres Seaver wrote:
A KGS needs to have the following properties:
- The "generation zero" of any KGS is an empty set of revisions.
- By default, any revision N of a KGS starts out as a "draft" version
which is an empty layer over version N-1. Changes to the draft
then shadow any version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Roger Ineichen wrote:
>> Hi Tres
>>
>>> Whoever released those two eggs (the '.dev-r#' ones) need
>>> to release "real" updated packages, and then grok 0.11.1
>>> should be released using them.
>>>
>>> DEATH TO FAUX PACKA
Philipp von Weitershausen wrote:
[snip]
So you're telling me that in order to define my own KGS (which anybody
should do for a serious project), I'll have to start deploying my own
index. For each project?
I think Grok should be using KGS by simply taking snapshots of it
sometimes and then bu
Roger Ineichen wrote:
Hi Tres
Whoever released those two eggs (the '.dev-r#' ones) need
to release "real" updated packages, and then grok 0.11.1
should be released using them.
DEATH TO FAUX PACKAGES!
As far as I understand, this does not happen if you
depend on a KGS, right?
Does th
Stephan Richter wrote:
On Friday 09 November 2007, Philipp von Weitershausen wrote:
It can't because you guys broke a dozen packages when you split up some
of the zope.app.* packages. I'm going to fix this now.
Can we stop pointing fingers, please?
Sorry for not sugar coating the facts. I gl
On Friday 09 November 2007, Philipp von Weitershausen wrote:
> It can't because you guys broke a dozen packages when you split up some
> of the zope.app.* packages. I'm going to fix this now.
Can we stop pointing fingers, please? I just spent 3-4 man-weeks to get the
packages to a decent state,
Stephan Richter wrote:
On Friday 09 November 2007, Roger Ineichen wrote:
Hi Tres
Whoever released those two eggs (the '.dev-r#' ones) need
to release "real" updated packages, and then grok 0.11.1
should be released using them.
DEATH TO FAUX PACKAGES!
As far as I understand, this does not
15 matches
Mail list logo
