From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: jjasen1@umbc.edu
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Releases
Date: Mon, 26 Nov 2001 11:46:31 +0100 [thread overview]
Message-ID: <3C021D87.E0390883@TeraPort.de> (raw)
> Re: Kernel Releases
>
>
> > Development kernels are development kernels... nothing else. Look to
> > distributors for high degrees of quality assurance testing. When you run a
> > development kernel you have joined the development team, even if you don't
> > know it. Finding and reporting bugs is your job...
>
> That's why you stay away from 2.5.x, or 2.4.x-pre, or 2.4.x-ac -- which
> are development kernels. 2.4.x kernels are released kernels.
>
The point being made (I believe) is that recently the "released"
kernels have had a low quality with showstopper-quality bugs being
introduced, but not detected, very late in the -preX cycle. What the
initiator of this thread wants is a longer testing of the last -preX
version. And changes between that an the "release" confined to bug/doc
fixing *only*. Whether this has to be under the "-rcX" label, or not -
the idea behind it is sound.
Martin
--
------------------------------------------------------------------
Martin Knoblauch | email: Martin.Knoblauch@TeraPort.de
TeraPort GmbH | Phone: +49-89-510857-309
C+ITS | Fax: +49-89-510857-111
http://www.teraport.de | Mobile: +49-170-4904759
next reply other threads:[~2001-11-26 10:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 10:46 Martin Knoblauch [this message]
2001-11-26 15:27 ` Kernel Releases John Jasen
2001-11-26 20:36 ` Horst von Brand
2001-11-27 2:40 ` Gerhard Mack
[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
[not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
-- strict thread matches above, loose matches on Subject: below --
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
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-25 4:27 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
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
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=3C021D87.E0390883@TeraPort.de \
--to=martin.knoblauch@teraport.de \
--cc=jjasen1@umbc.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox