[Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marius Gedminas wrote: > On Wed, Jul 11, 2007 at 02:13:46PM -0400, Tres Seaver wrote: >> Fred Drake wrote: >>> On 7/11/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: Right, I made the same assumption: the eggs have been set free, >>> >>>

Re: [Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Marius Gedminas
On Wed, Jul 11, 2007 at 02:13:46PM -0400, Tres Seaver wrote: > Fred Drake wrote: > > On 7/11/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: > >> Right, I made the same assumption: the eggs have been set free, > > > > Right. No need to hold all the developers hostage to a release model >

Re: [Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benji York wrote: > Tres Seaver wrote: > > [1] This means *never* doing 'svn mv' or 'svn remove' on such a tag, > > once announced. No exceptions, period, even for "brown bags". > > I can see that rule applying to eggs, but I'm not sure why we

Re: [Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Benji York
Tres Seaver wrote: > [1] This means *never* doing 'svn mv' or 'svn remove' on such a tag, > once announced. No exceptions, period, even for "brown bags". I can see that rule applying to eggs, but I'm not sure why we need to do it for tags. I don't really object, but would like to understand

[Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred Drake wrote: > On 7/11/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: >> Right, I made the same assumption: the eggs have been set free, > > Right. No need to hold all the developers hostage to a release model > we've been working to g

Re: [Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Fred Drake
On 7/11/07, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: Right, I made the same assumption: the eggs have been set free, Right. No need to hold all the developers hostage to a release model we've been working to get away from. -Fred -- Fred L. Drake, Jr. "Chaos is the score upo

Re: [Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Philipp von Weitershausen
Fred Drake wrote: On 7/10/07, Christian Theune <[EMAIL PROTECTED]> wrote: We never said anything else. We planned for some future to stop doing that, I never saw a proposal get accepted that changes the release in this way. Did I miss something? Interesting. I don't recall seeing anyone menti

Re: [Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Fred Drake
On 7/10/07, Christian Theune <[EMAIL PROTECTED]> wrote: We never said anything else. We planned for some future to stop doing that, I never saw a proposal get accepted that changes the release in this way. Did I miss something? Interesting. I don't recall seeing anyone mention a 3.5 release at

Re: [Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-11 Thread Christian Theune
Am Dienstag, den 10.07.2007, 17:37 +0300 schrieb Philipp von Weitershausen: > Christian Theune wrote: > > Am Dienstag, den 03.07.2007, 10:31 +0300 schrieb Gary Poster: > >> Christian et al: > >> > >> What do you want in regards to the zope.app.session changes that rely > >> on the new package zop

[Zope3-dev] Re: zope.app.session/zope.minmax

2007-07-10 Thread Philipp von Weitershausen
Christian Theune wrote: Am Dienstag, den 03.07.2007, 10:31 +0300 schrieb Gary Poster: Christian et al: What do you want in regards to the zope.app.session changes that rely on the new package zope.minmax? Very briefly, the change allows the simple zope.app.session approach to cause fewer u