From: Ian Stirling <root@mauve.demon.co.uk>
Message-Id: <200111261451.OAA03381@mauve.demon.co.uk>
Subject: Re: Kernel Releases
To: linux@sneulv.dk (Allan Sandfeld)
Date: Mon, 26 Nov 2001 14:51:48 +0000 (GMT)
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <E168HyH-0000xw-00@Princess> from "Allan Sandfeld" at Nov 26, 2001 10:22:36 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

> 
> On Sunday 25 November 2001 05:27, David Relson wrote:
> 
> <snip>
> > When the kernel maintainer, now Marcelo for 2.4, is ready to release the
> > next kernel, for example 2.4.16, I suggest he switch from "pre?" to "-rc1"
<snip>
> Like Linus said, it's a statistical problem: An unofficial kernel would never 
> get the same attention as a released one. We would keep seeing problems arise 
> once the kernel has been released. 
True.
However, I for one never run a -pre kernel.
I am unfortunately not wealthy, so am at the trailing edge of hardware 
(Athlon 550, P100 laptop, ...) so I rarely need devices only in the 
latest kernels.
I do however occasionally run new kernels on boxes at various times.
I don't run -pre, because rightly or wrongly, I've got the impression that
these get even less testing than releases.
I might well run -rcn kenrels, as these are presumably tested a little more,
and thought to be a little more stable.
This would help make me part of the solution, rather than part of the problem.
(complaining when 2.4.10 falls on it's face whenever something reads lots
of data say, or 2.4.11 has link problems)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/