All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: John Alvord <jalvo@mbay.net>
Cc: David Relson <relson@osagesoftware.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel Releases
Date: Sun, 25 Nov 2001 17:34:29 +1100	[thread overview]
Message-ID: <20011125173429.C662@zip.com.au> (raw)
In-Reply-To: <4.3.2.7.2.20011124231412.00b40c50@mail.osagesoftware.com> <Pine.LNX.4.20.0111242147500.26049-100000@otter.mbay.net>
In-Reply-To: <Pine.LNX.4.20.0111242147500.26049-100000@otter.mbay.net>

On Sat, Nov 24, 2001 at 09:49:39PM -0800, John Alvord wrote:
> Development kernels are development kernels... nothing else. Look to
> distributors for high degrees of quality assurance testing. When you run a
> development kernel you have joined the development team, even if you don't
> know it. Finding  and reporting bugs is your job...

2.x.y, where x is even, is not a development kernel. It's a release kernel.
2.x.y, where x is odd is a development kernel
2.x.yprez is a development kernel

I think his point is that recently, 2.x.y where x is even has been of
the same quality as a development kernel. Blatantly nasty bugs are in it
and they really shouldn't be. And so, in order to test things out better
he effectively saying that putting a -rcz tag on it will help as it'll
indicate a release candidate and as such might get more ppl to use it.
Once no obvious issues show up with those, put it as a release.

No real extra work required. You just need to make a decision of 'enough
stuffing about. I wanna make a release soon' and start labelling
acordingly. This doesn't mean -rcz will be release quality. It just
means that it's close to it. It still wont mean it's 100% bug free but
it's an extra chance to catch the bad stuff.

All in all, it's not a bad idea[tm].

-- 
CaT        "As you can expect it's really affecting my sex life. I can't help
           it. Each time my wife initiates sex, these ejaculating hippos keep
           floating through my mind."
                - Mohd. Binatang bin Goncang, Singapore Zoological Gardens

  reply	other threads:[~2001-11-25  6:35 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25  4:27 Kernel Releases David Relson
2001-11-25  5:49 ` John Alvord
2001-11-25  6:34   ` CaT [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-11-25  5:37 Dan Kegel
2001-11-25  9:25 ` Nathan Dabney
2001-11-25 10:24   ` Keith Owens
2001-11-25 13:34     ` Phil Howard
2001-11-25 19:03     ` Nathan Dabney
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-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
     [not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
     [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

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=20011125173429.C662@zip.com.au \
    --to=cat@zip.com.au \
    --cc=jalvo@mbay.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=relson@osagesoftware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.