-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Hey,
>
> Another point of feedback:
>
> I saw Stephan's mail on a (partially new) toolchain and somewhat
> extensive workflow on using it. I'm a bit surprised a toolchain is
> necessary and that the workflow is so involved.
Jim Fulton wrote:
[snip]
Let me make the case for bug-for-bug compatibility:
I assume by this you mean setting fixed versions.
Yes.
[snip]
I'm not suggesting that setting fixed versions is a bad idea. I think
some projects may choose to go this way. This is a valid policy
decision. Othe
On Oct 7, 2007, at 7:33 AM, Lennart Regebro wrote:
On 10/6/07, Jim Fulton <[EMAIL PROTECTED]> wrote:
Only people who ask for updates.
Which by default is every time somebody runs a buildout, right?
Yes
I think this depends on the use cases. I think most people would
like to get bug fixe
On Oct 6, 2007, at 6:07 PM, Martijn Faassen wrote:
Jim Fulton wrote:
On Oct 6, 2007, at 5:24 AM, Martijn Faassen wrote:
[snip]
What I really don't like about this proposal is that it talks
about updating index pages. If I understand this right, an
updated index page will force everybody t
On 10/6/07, Jim Fulton <[EMAIL PROTECTED]> wrote:
> Only people who ask for updates.
Which by default is every time somebody runs a buildout, right?
> I think this depends on the use cases. I think most people would
> like to get bug fixes. The intent of such a 3.4 index would be to
> give peop
Jim Fulton wrote:
On Oct 6, 2007, at 5:24 AM, Martijn Faassen wrote:
[snip]
What I really don't like about this proposal is that it talks about
updating index pages. If I understand this right, an updated index
page will force everybody that uses this index page into an update.
Only people
On Oct 6, 2007, at 5:24 AM, Martijn Faassen wrote:
Hey,
I'm glad some steps are taken!
What I really don't like about this proposal is that it talks about
updating index pages. If I understand this right, an updated index
page will force everybody that uses this index page into an update.
Jim Fulton wrote:
I discussed this a bit this afternoon with Stephan and we came up with
an idea that we think might help. Stephan is going to try to prototype
it. I'll try to explain it.
snip
Hopefully, this will give us much greater stability than we've had up to
now.
For what it is wo
Hey,
Another point of feedback:
I saw Stephan's mail on a (partially new) toolchain and somewhat
extensive workflow on using it. I'm a bit surprised a toolchain is
necessary and that the workflow is so involved. With Grok's approach
using extends in buildout, we can just publish such a list o
Benji York wrote:
Stephan Richter wrote:
2. How many packages should be controlled in this index? I think we
should definitely add packages from z3c and the zc namespace.
What is the motivation to include non-controlled packages? I suppose it
is to let people use those packages with (in this
Stephan Richter wrote:
On Friday 05 October 2007 22:45, Benji York wrote:
Stephan Richter wrote:
2. How many packages should be controlled in this index? I think we
should definitely add packages from z3c and the zc namespace.
What is the motivation to include non-controlled packages?
Jim me
Hey,
I'm glad some steps are taken!
What I really don't like about this proposal is that it talks about
updating index pages. If I understand this right, an updated index page
will force everybody that uses this index page into an update. I don't
think this is acceptable. Instead I'd suggest
12 matches
Mail list logo
