From: Justin Wells <jread@semiotek.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Please tag tested releases of the 2.4.x kernel
Date: Sun, 2 Dec 2001 18:38:36 -0500 [thread overview]
Message-ID: <20011202183836.A32423@semiotek.com> (raw)
Christoph Hellwig wrote:
> In article <20011201113734.5187E38329@fever.semiotek.com> you wrote:
> > And the kernels on kernel.org *are* tested, by lots of people, by kernel
> > developers, by lots of ordinary folks even. I bet right after theren's
> > an announce on slashdot you see lots of traffic on the ftp/http sites.
>
> The problem is that there is absoloutly no defined QA-cycle for these
> kernels. Please take a look at what distributors (at least most, I know
> at least one counter-example):
I'm not asking for any change in the development process, the
creation of a test suite, or any quantification of quality. I'm
asking for the consensus.
Here's my level of comfort: I don't want to be on the bleeding edge,
but I want to be on the blade, just a little back from where all the
bloodshed is. I want to run something pretty new, but which lots of
other people have been able to run without much pain.
The voting idea sounded good, or just tracking what people are running,
or having someone judge the consensus by gut feel. Any of these would
guide people like me to the better kernels.
I just want to see some indicator like this on kernel.org pointing me at
which kernels are worth my while to test out and try.
Justin
next reply other threads:[~2001-12-03 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 23:38 Justin Wells [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-01 1:05 Please tag tested releases of the 2.4.x kernel willy tarreau
2001-12-01 1:10 ` Mike Fedyk
2001-12-01 2:42 ` Ian Stirling
2001-12-01 2:53 ` Mike Fedyk
2001-12-01 11:31 ` Miquel van Smoorenburg
2001-11-30 22:04 Justin Wells
2001-11-30 23:15 ` Mike Fedyk
2001-12-01 0:28 ` Mike Fedyk
2001-12-01 9:41 ` Christoph Hellwig
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=20011202183836.A32423@semiotek.com \
--to=jread@semiotek.com \
--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