public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Dan Kegel <dank@kegel.com>, Fran?ois Cami <stilgar2k@wanadoo.fr>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Releases
Date: Wed, 28 Nov 2001 11:17:18 -0800	[thread overview]
Message-ID: <20011128111718.A513@mikef-linux.matchmail.com> (raw)
In-Reply-To: <dank@kegel.com> <3C03CFA7.3E824AE7@kegel.com> <200111281623.fASGN7lC015061@pincoya.inf.utfsm.cl>
In-Reply-To: <200111281623.fASGN7lC015061@pincoya.inf.utfsm.cl>

On Wed, Nov 28, 2001 at 01:23:07PM -0300, Horst von Brand wrote:
> Dan Kegel <dank@kegel.com> said:
> > Fran?ois Cami wrote:
> 
> [...]
> 
> > > That said, I think the week long delay is a *good* idea.
> 
> > It's the key to avoiding bad releases.
> 
> Yep. Specially when new 2.5.X-preY or 2.5.X are generated at a rate of 2 or
> 3 a week. Look at the history of the kernel. This would only create even
> _more_ pressure to get new patches in, and that is bad.

2.5 doesn't have releases, just snapshots of the development.

> 
> When a freeze (or slush) is decreed at the very end, it makes sense.
> Remember that a large part of the success of Linux is due to "Release
> early, release often".

Remember we are talking about 2.4, not 2.5.  Having more time between
releases gives more time to test the pre releases.  The point it to have
good point (not like 2.4.11, 12, 14, or 15) releases for what is supposed to
be *stable*.

Release 50 -pre kernels for 2.4, but make sure that the next release has had a
chance to stabalize with the new changes.

MF

  reply	other threads:[~2001-11-28 19:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27 17:25 Kernel Releases 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 [this message]
     [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-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  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-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=20011128111718.A513@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stilgar2k@wanadoo.fr \
    --cc=vonbrand@inf.utfsm.cl \
    /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