From: Larry McVoy <lm@bitmover.com>
To: Tim Cambrant <tim@cambrant.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Too soon for stable release?
Date: Sat, 29 Nov 2003 09:01:04 -0800 [thread overview]
Message-ID: <20031129170104.GA15333@work.bitmover.com> (raw)
In-Reply-To: <20031129174916.GA4592@cambrant.com>
On Sat, Nov 29, 2003 at 06:49:16PM +0100, Tim Cambrant wrote:
> I am sorry if this offends someone or if I'm totally on the wrong track
> here, but it seems odd to actually call the Beaver On Detox "stable",
> considering the amount of misc. problems people have been having the
> last week with -test11.
The "stable" series of the kernel is never really stable for a while.
A better way to think of it is as "that place where things become stable
by refusing to take any new changes except bug fixes".
The news media hasn't picked up on this yet, they seem to think that
2.6.0 is something that will be useful. It won't be, there will be a
period of months during which things stablize and then you'll see the
distros pick up the release. I don't remember where it was exactly
(2.4.18?) but Red Hat waited quite a while before switching to 2.4
from 2.2. This is normal and it works out quite well in practice.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-11-29 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 17:49 Too soon for stable release? Tim Cambrant
2003-11-29 17:01 ` Larry McVoy [this message]
2003-11-29 17:11 ` Russell King
2003-11-29 17:42 ` Arjan van de Ven
2003-11-29 20:22 ` Stan Bubrouski
2003-11-29 17:16 ` William Lee Irwin III
2003-12-01 18:56 ` Mike Fedyk
2003-11-29 18:03 ` Tim Cambrant
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=20031129170104.GA15333@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@cambrant.com \
/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;
as well as URLs for NNTP newsgroup(s).