public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
Date: 5 Jan 2001 09:31:27 -0800	[thread overview]
Message-ID: <9350df$2md$1@penguin.transmeta.com> (raw)
In-Reply-To: <3A55447D.995FB159@goingware.com>

In article <3A55447D.995FB159@goingware.com>,
Michael D. Crawford <crawford@goingware.com> wrote:
>
>I understand Linus' desire to have more widespread testing done on the kernel,
>and certainly he can accomplish that by labeling some random build as the new
>stable version.  But I think a better choice would have been to advocate testing
>more widely - don't just announce it to the linux-kernel list, get on National
>Public Radio, the Linux Journal and Slashdot and stuff.  

You don't understand people, I think. 

No amount of publicity will matter all that much in the end: yes, it
will result in many people who are not afraid of a compiler to try it
out. And we've had that for over six months now, realistically.

But that's very different from having somebody like RedHat, SuSE or
Debian make such a kernel part of their standard package. No, I don't
expect that they'll switch over completely immediately: that would show
a lack of good judgement. The prudent approach has always been to have
both a 2.2.19 and a 2.4.0 kernel on there, and ask the user if he wants
to test the new kernel first.

That way you get a completely different kind of user that tests it.

The other thing is that even if something like 2.4.0-test8 gets rave
reviews, that doesn't _matter_ to people who crave stability. The fact
is that 2.4.0 has been getting quite a lot of testing: people haven't
even seen how the big vendors have all done testing in their labs etc.

And to the people who really want to have stability, none of that
matters.  They will basically "start fresh" at the 2.4.0 release, and
give it a few months just to follow the kernel list etc to see what the
problems will be.  They'll have people starting to ramp up 2.4.0 kernels
in their own internal test environment, moving it first to machines they
feel more comfortable with etc etc. 

None of which would happen if you just try to make the beta testing
cycle much bigger. 

Which is why to _me_ the most important thing is that I'm happy with the
core infrastructure - because once you've tested it to a certain degree,
it's not going to improve without a real public release.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-05 17:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  3:50 Change of policy for future 2.2 driver submissions Michael D. Crawford
2001-01-05  8:29 ` Miles Lane
2001-01-05 17:31 ` Linus Torvalds [this message]
2001-01-09 14:49   ` Hubert Mantel
2001-01-09 14:54     ` Alan Cox
2001-01-09 23:49       ` Jakob Østergaard
2001-01-10  0:02         ` Linus Torvalds
2001-01-10  0:33     ` Ingo Molnar
2001-01-10  1:03       ` Andrea Arcangeli
2001-01-10  1:17         ` Ingo Molnar
2001-01-10  1:40           ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:36 Wayne.Brown
2001-01-08  4:52 Wayne.Brown
2001-01-08 11:07 ` David Weinehall
2001-01-05 20:33 Wayne.Brown
2001-01-06 10:15 ` Nick Holloway
2001-01-05 17:32 Wayne.Brown
2001-01-05 18:50 ` Matthew D. Pitts
2001-01-05 17:11 Wayne.Brown
2001-01-05 17:15 ` Alan Cox
2001-01-05 17:23   ` Christoph.Hellwig.
     [not found]     ` <hchÀcaldera.de>
2001-01-05 17:31       ` Alan Cox
2001-01-05  2:41 Alan Cox
2001-01-05  3:27 ` Nicholas Knight
2001-01-05  4:23   ` Mark Hahn
2001-01-05 12:52     ` Daniel Phillips
2001-01-05  6:38   ` Tim Riker
2001-01-05  6:57   ` Andre Tomt
2001-01-05  7:30     ` Gerhard Mack
2001-01-05 11:46   ` Rik van Riel

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='9350df$2md$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.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