Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?)from the Vancouver release team meeting)

2005-03-21 Thread Ola Lundqvist
On Sat, Mar 19, 2005 at 09:36:38AM -0600, Gunnar Wolf wrote: > Ola Lundqvist dijo [Tue, Mar 15, 2005 at 09:19:45PM +0100]: > > > And would a larger discussion at debconf'05 not have been more appropriate > > > than handing done a couple of taken decision disguised as proposal ? > > > > > > It is

Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?)from the Vancouver release team meeting)

2005-03-19 Thread Gunnar Wolf
Ola Lundqvist dijo [Tue, Mar 15, 2005 at 09:19:45PM +0100]: > > And would a larger discussion at debconf'05 not have been more appropriate > > than handing done a couple of taken decision disguised as proposal ? > > > > It is not too late for this yet, but there needs to be a real discussion > >

Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-15 Thread Ola Lundqvist
Hello On Tue, Mar 15, 2005 at 12:43:11AM +0100, Sven Luther wrote: > On Mon, Mar 14, 2005 at 05:32:44PM -0500, Joey Hess wrote: > > Frank Küster wrote: > > > I do not understand why the Nybbles team mixed their good news about > > > sarge with their foreseeably controversial plans or proposal for

Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-15 Thread Joey Hess
Julien BLACHE wrote: > It has absolutely nothing to do with what has been discussed > previously. The authors are the same who said repeteadly that the > number of architectures wasn't reponsible for the sarge delay. The above statement is incorrect. If you disagree, you'll need to pull up referen

Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-15 Thread Julien BLACHE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Perrier <[EMAIL PROTECTED]> wrote: > OK, the architecture handling is controversial. Fine...this will > probably delay etch more than we would like. But could we please focus > on releasing sarge first? By focus, I also mean avoidn wasting >

Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-15 Thread Christian Perrier
> I do not understand why the Nybbles team mixed their good news about > sarge with their foreseeably controversial plans or proposal for etch. This may have been a strategical error, yes. For me, the Vancouver meeting goal was obviously the sarge release and IMHO, they achieved their goal very

Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Sven Luther
On Mon, Mar 14, 2005 at 05:32:44PM -0500, Joey Hess wrote: > Frank Küster wrote: > > I do not understand why the Nybbles team mixed their good news about > > sarge with their foreseeably controversial plans or proposal for etch. > > I fear that we will have a huge, long flamewar. And many competen

Re: Release sarge now, or discuss etch issues? (was: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Joey Hess
Frank Küster wrote: > I do not understand why the Nybbles team mixed their good news about > sarge with their foreseeably controversial plans or proposal for etch. > I fear that we will have a huge, long flamewar. And many competent, > active people will start coding implementations of alternative

Release sarge now, or discuss etch issues? (was: Bits (Nybbles?) from the Vancouver release team meeting)

2005-03-14 Thread Frank Küster
Christian Perrier <[EMAIL PROTECTED]> wrote: > ...but quite sad (or happy?) to see that nearly only the proposal to handle > architectures differently got criticism...while this proposal contains > several other key point. I do not understand why the Nybbles team mixed their good news about sarge