Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)

[=?ISO-8859-15?Q?Fran=E7ois?= Cami]

Matthew D. Pitts wrote:

> Umm... Linus, when are you going to open the 2.5.x development cycle? That
> is how we used to catch this kind of thing.

*eager to test 2.5* I guess that's one good idea, yes... less 'beta' in
the current 'stable' tree means that there actually is a dev tree.

And we're back at what Sean Elble wrote about SGI having two
trees for IRIX.

François

> Matthew D. Pitts
> Pitts Computer Services
> [e-mail]
> ----- Original Message -----
> From: "François Cami" <[e-mail]>
> To: "Sean Elble" <[e-mail]>
> Cc: <[e-mail]>; "John Alvord" <[e-mail]>;
> <[e-mail]>
> Sent: Monday, November 12, 2001 8:03 PM
> Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop
> back broken in 2.2.14)
> 
> 
> 
>>I am wondering too... Anyone got ideas on this ?
>>
>>I would like to avoid some specific problems... especially
>>bugs that show up when compiling a certain module / feature
>>of the kernel, like the loopback in 2.4.14.
>>
>>Those should be very easy to get rid of
>>[it only takes some kernel testers to debug that early, if only
>>there actually were a feature freeze that last for one day...].
>>
>>François
>>
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
>