Santiago Vila <[EMAIL PROTECTED]> writes:
> * "unstable" is actually frozen, which means uploads for unstable are
> either discouraged, they remain in the limbo, or they are automatically
> put in some other distribution above unstable, like new-unstable, until
> testing or unstable becomes the ne
On Tue, May 31, 2005 at 11:36:06AM +0200, Thijs Kinkhorst wrote:
> On Tue, May 31, 2005 03:43, Miles Bader wrote:
> > Bernd Eckenfels <[EMAIL PROTECTED]> writes:
> >> Actually I am glad somebody is working public visible on the release
> >> issues and would not critisize him for that.
> >
> > Point
On Tue, May 31, 2005 at 11:22:20AM +0200, Adrian Bunk wrote:
> > I noticed that Adrian moved a bug report for a kernel in sid (2.6.10
> > IIRC) to the 2.6.8 kernel so it appeared as a Sarge RC Bug? I didn't
> > see anything that showed that it was a 2.6.8 problem, maybe it is, but
> > it looked li
On Tue, May 31, 2005 03:43, Miles Bader wrote:
> Bernd Eckenfels <[EMAIL PROTECTED]> writes:
>> Actually I am glad somebody is working public visible on the release
>> issues and would not critisize him for that.
>
> Pointing out a problem is nice, but doing so in an obnoxious manner
> hurts.
I wo
On Tue, 31 May 2005, Adrian Bunk wrote:
> On Mon, May 30, 2005 at 03:45:07PM -0400, Joey Hess wrote:
> > Adrian Bunk wrote:
> > > Or do you _really_ want to release sarge with many dozens of already
> > > known and fixed bugs?
> >
> > I'd worry about it more if we hadn't suffered from the same o
On Tue, May 31, 2005 at 04:07:11PM +1200, Nigel Jones wrote:
> I noticed that Adrian moved a bug report for a kernel in sid (2.6.10
> IIRC) to the 2.6.8 kernel so it appeared as a Sarge RC Bug? I didn't
> see anything that showed that it was a 2.6.8 problem, maybe it is, but
> it looked like seco
On Mon, May 30, 2005 at 03:45:07PM -0400, Joey Hess wrote:
> Adrian Bunk wrote:
> > Or do you _really_ want to release sarge with many dozens of already
> > known and fixed bugs?
>
> I'd worry about it more if we hadn't suffered from the same or similar
> problems with ever previous Debian releas
I noticed that Adrian moved a bug report for a kernel in sid (2.6.10
(BIIRC) to the 2.6.8 kernel so it appeared as a Sarge RC Bug? I didn't
(Bsee anything that showed that it was a 2.6.8 problem, maybe it is, but
(Bit looked like second guessing to me...
(B
(BHow is this helping Sarge? If it
Bernd Eckenfels <[EMAIL PROTECTED]> writes:
(B> Actually I am glad somebody is working public visible on the release issues
(B> and would not critisize him for that.
(B
(BPointing out a problem is nice, but doing so in an obnoxious manner
(Bhurts.
(B
(B-Miles
(B--
$B<+$i$r6u$K$7$F!"?4$r3+
Adrian Bunk wrote:
> Or do you _really_ want to release sarge with many dozens of already
> known and fixed bugs?
I'd worry about it more if we hadn't suffered from the same or similar
problems with ever previous Debian release, TBPH. Even back when we froze
unstable, this just pushed certian bug
In article <[EMAIL PROTECTED]> you wrote:
> Do you think you could manage to leave your critisms til next week when
> we might have released and turn them into constructive criticisms
> instead of merely demanding pieces of information from the release team?
He is warning about a big number of onr
Russ Allbery wrote:
>Adrian Bunk <[EMAIL PROTECTED]> writes:
>
>> Or do you _really_ want to release sarge with many dozens of already
>> known and fixed bugs?
>
>Yes. Given the number of packages in Debian, some amount of this is
>inevitable. We'll live.
>
>And you're not just providing constru
Adrian Bunk <[EMAIL PROTECTED]> writes:
> Or do you _really_ want to release sarge with many dozens of already
> known and fixed bugs?
Yes. Given the number of packages in Debian, some amount of this is
inevitable. We'll live.
And you're not just providing constructive feedback. You're also
On Mon, May 30, 2005 at 12:17:29PM +0100, Simon Huggins wrote:
> Adrian, I've noticed lately that almost every post you send is about the
> release; Pointing out problems with some feature or other of it or with
> the actions of the hard working people who are trying to get sarge out
> the door.
>
Adrian, I've noticed lately that almost every post you send is about the
release; Pointing out problems with some feature or other of it or with
the actions of the hard working people who are trying to get sarge out
the door.
Do you think you could manage to leave your critisms til next week when
15 matches
Mail list logo
