From: Allan Sandfeld <linux@sneulv.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel Releases
Date: Mon, 26 Nov 2001 10:22:36 +0100 [thread overview]
Message-ID: <E168HyH-0000xw-00@Princess> (raw)
In-Reply-To: <4.3.2.7.2.20011124231412.00b40c50@mail.osagesoftware.com>
In-Reply-To: <4.3.2.7.2.20011124231412.00b40c50@mail.osagesoftware.com>
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"
> (as in release candidate). A day or two with -rc1 will quickly show if it
> has a show stopper. If so, then the minor fixes (and nothing else) go into
> -rc2. A day or two ..., and either -rc3 appears or we have a stable
> release and 2.4.16 is ready to be released.
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.
One thing we could do, was to do the same as the vendors do, and maintain a
-post kernel with the most glaring bug-fixed, especially build-ones.
The need to do it however is not that big..
next prev parent reply other threads:[~2001-11-26 9:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 4:27 Kernel Releases David Relson
2001-11-25 5:49 ` John Alvord
2001-11-25 6:34 ` CaT
2001-11-25 14:12 ` John Jasen
2001-11-26 7:15 ` John Alvord
2001-11-25 15:46 ` Eric W. Biederman
2001-11-25 16:23 ` Nathan Walp
2001-11-26 21:03 ` Bill Davidsen
2001-11-25 19:55 ` Phil Sorber
2001-11-26 9:22 ` Allan Sandfeld [this message]
2001-11-26 14:51 ` Ian Stirling
2001-11-26 15:02 ` Rik van Riel
2001-11-26 19:11 ` Ian Stirling
2001-11-26 19:55 ` vda
2001-11-26 20:42 ` Bill Davidsen
2001-11-27 4:21 ` Mike Fedyk
2001-11-27 9:50 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2001-11-25 5:37 Dan Kegel
2001-11-25 9:25 ` Nathan Dabney
2001-11-25 10:24 ` Keith Owens
2001-11-25 13:34 ` Phil Howard
2001-11-25 19:03 ` Nathan Dabney
2001-11-26 10:46 Martin Knoblauch
2001-11-26 15:27 ` John Jasen
2001-11-26 20:36 ` Horst von Brand
2001-11-27 2:40 ` Gerhard Mack
2001-11-27 17:25 Dan Kegel
2001-11-27 17:36 ` François Cami
2001-11-27 17:38 ` Dan Kegel
2001-11-27 18:13 ` Vitaly Luban
2001-11-28 16:23 ` Horst von Brand
2001-11-28 19:17 ` Mike Fedyk
[not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
[not found] <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>
2001-11-27 18:08 ` vda
2001-11-27 16:58 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E168HyH-0000xw-00@Princess \
--to=linux@sneulv.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.