From: Christoph Hellwig <hch@ns.caldera.de>
To: jread@semiotek.com (Justin Wells)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: Please tag tested releases of the 2.4.x kernel
Date: Sat, 1 Dec 2001 13:00:48 +0100 [thread overview]
Message-ID: <200112011200.fB1C0m711338@ns.caldera.de> (raw)
In-Reply-To: <20011201113734.5187E38329@fever.semiotek.com>
[It would be nice f you could teach your mailer about replies..]
Hi Justin,
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):
o they freeze at one public kernel release
o they do testing, lots of testing
o they apply bugfixes for problems found in their debugging
or coming in new releases _only_. No new major changes that
might break things.
That's why new distribution releases tend to come with 'old-looking'
kernels.
With kernel.org release _any_ new release mixes features, rewrites and
bugfixes. I hope this will change a little for 2.4 now that Marcelo
who does the above cycle for for Conectiva takes over maintainership.
But in can't in whole - noone would really freeze the stable series
as strict as distributors do.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-12-01 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 11:37 Justin Wells
2001-12-01 12:00 ` Christoph Hellwig [this message]
2001-12-01 19:51 ` Colonel
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=200112011200.fB1C0m711338@ns.caldera.de \
--to=hch@ns.caldera.de \
--cc=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
all inboxes | Powered by JetHome®