public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: David Relson <relson@osagesoftware.com>, stp@osdlab.org
Subject: re: Kernel Releases
Date: Sat, 24 Nov 2001 21:37:38 -0800	[thread overview]
Message-ID: <3C0083A2.A817BFE@kegel.com> (raw)

David Relson <relson@osagesoftware.com> wrote:
> With the recent problems, the working 
> versions tend to be the -pre1 or -pre2 releases, not the released 
> one.  With a bit of QA, I think we can have 2.4.x releases be the stable 
> releases.  Here's how...
> 
> When the kernel maintainer, now Marcelo for 2.4, is ready to release the 
> next kernel, for example 2.4.16, I suggest he switch from "pre?" to "-rc1" 
> (as in release candidate).  A day or two with -rc1 will quickly show if it 
> has a show stopper.  If so, then the minor fixes (and nothing else) go into 
> -rc2.  A day or two ..., and either -rc3 appears or we have a stable 
> release and 2.4.16 is ready to be released.
> 
> Let's go the extra distance and have the releases be usable, stable 
> kernels!  It's what users want and it's within the abilities of the 
> developers to produce.  Let's do it :-)

Hear, hear!  

Also, Marcelo should get in touch with the nice folks at stp@osdlab.org
and find out what sort of regression tests they will be running on
his kernels.  Perhaps he can wait for their feedback on the -rcX
kernels before declaring them final.  (Not that they would have
found the 2.4.15 problem with their current tests, but they'll
catch a few things.)

- Dan

             reply	other threads:[~2001-11-25  5:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25  5:37 Dan Kegel [this message]
2001-11-25  9:25 ` Kernel Releases Nathan Dabney
2001-11-25 10:24   ` Keith Owens
2001-11-25 13:34     ` Phil Howard
2001-11-25 19:03     ` Nathan Dabney
     [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-26 10:46 Martin Knoblauch
2001-11-26 15:27 ` John Jasen
2001-11-26 20:36   ` Horst von Brand
2001-11-27  2:40     ` Gerhard Mack
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=3C0083A2.A817BFE@kegel.com \
    --to=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=relson@osagesoftware.com \
    --cc=stp@osdlab.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