All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: espenfjo@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: My thoughts on the "new development model"
Date: Sat, 23 Oct 2004 07:52:12 +0200	[thread overview]
Message-ID: <20041023055212.GA21206@alpha.home.local> (raw)
In-Reply-To: <20041023014004.GG22558@stusta.de>

Hi Adrian,

On Sat, Oct 23, 2004 at 03:40:04AM +0200, Adrian Bunk wrote:
 
> 2.6.9 -> 2.6.10-rc1:
> - 4 days
> - > 15 MB patches

I firmly agree, and that's one of the reasons I still don't use 2.6. This
could be avoided with a shorter release cycle with far less new features
for each version (a bit like openbsd does), because about every maintainer
would have a valid base to work on for the next release or the one after,
and would not try to push unstable code in the "stable" kernel. Today, lots
of people are certain that 2.8 (or 3.0) won't be out before 3 or 4 years. So
if they want their code released soon, they push it hard in the current
mainline :-(

> It's a bit optimistic to call this amount of change "stabilizing".

What really frightens me is that judging from the changelogs, it really
looks like cleanups, bug fixes and sometimes core changes... This gives
a terrible idea of previous release code !

> 2.6 is corrently more a development kernel than a stable kernel.

That's how I present it to friends and customers too ;-) To others, I simply
say that it's the new stable kernel, and I observe how it works for them :-)

> The last bug I observed personally was the problem with suspending when 
> using CONFIG_REGPARM=y together with Roland's waitid patch which was 
> added in 2.6.9-rc2. If I'd used 2.6.9 with the same .config as 2.6.8.1, 
> this was simple one more bug...

Each time I try a new release, I barely find it extremely slow and unstable,
and I don't know where to start from to report broken things... Unfortunately
I don't have enough time to spend on bug reports these days so I stick to a
stable 2.4.

> IMHO Andrew+Linus should open a short-living 2.7 tree soon and Andrew 
> (or someone else) should maintain a 2.6 tree with less changes (like 
> Marcelo did and does with 2.4).

Yes, but not until the core is stabilized. Otherwise, ever changing features
and exports will discourage driver maintainers from backporting fixes.

Willy
 

  parent reply	other threads:[~2004-10-23  6:06 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 20:03 My thoughts on the "new development model"(A bit late tho) Espen Fjellvær Olsen
2004-10-22 21:52 ` My thoughts on the "new development model" Espen Fjellvær Olsen
2004-10-22 22:12   ` Clemens Schwaighofer
2004-10-23 12:55     ` Bernd Petrovitsch
2004-10-24  3:04       ` Clemens Schwaighofer
2004-10-22 22:45   ` William Lee Irwin III
2004-10-22 22:50     ` Espen Fjellvær Olsen
2004-10-22 23:21       ` William Lee Irwin III
2004-10-23  0:41       ` Lee Revell
2004-10-22 22:57   ` Willy Tarreau
2004-10-23  0:09     ` William Lee Irwin III
2004-10-23  2:40       ` Lee Revell
2004-10-25 21:15       ` Bill Davidsen
2004-10-25 22:08         ` William Lee Irwin III
2004-10-26 16:12         ` Charles Shannon Hendrix
2004-10-26 16:53           ` Mark Nipper
2004-10-23  1:40     ` Adrian Bunk
2004-10-23  5:04       ` Greg KH
2004-10-26  1:07         ` Adrian Bunk
2004-10-23  5:52       ` Willy Tarreau [this message]
2004-10-23 14:18         ` William Lee Irwin III
2004-10-23 19:58       ` Kronos
2004-10-23 20:05         ` Espen Fjellvær Olsen
2004-10-22 22:58   ` Lee Revell
2004-10-22 23:21     ` Paul Fulghum
2004-10-22 23:43     ` William Lee Irwin III
2004-10-23  8:01     ` Boris Bukowski
2004-10-23 13:27       ` My thoughts on the Alban Browaeys
2004-10-23 23:22         ` Boris Bukowski
2004-10-26 16:01   ` My thoughts on the "new development model" John Richard Moser
2004-10-26 16:44     ` John Richard Moser
2004-10-26 16:58       ` Hua Zhong
2004-10-26 18:53         ` Diego Calleja
2004-10-26 19:33           ` Paul Fulghum
2004-10-27 15:31             ` Alan Cox
2004-10-27 15:30         ` Alan Cox
2004-10-27 18:37           ` Hua Zhong
2004-10-27 21:39             ` Alan Cox
2004-10-27 22:51               ` That's it - " Hua Zhong
2004-10-27 16:59         ` Arjan van de Ven
2004-10-27 19:27           ` Marcos D. Marado Torres
2004-10-26 18:01     ` Stephen Hemminger
2004-10-26 18:38       ` John Richard Moser
  -- strict thread matches above, loose matches on Subject: below --
2004-10-26  5:40 Chuck Ebbert
2004-10-26 10:44 ` Ed Tomlinson
2004-10-26 11:09   ` Massimo Cetra
2004-10-26 12:08     ` Paolo Ciarrocchi
2004-10-26 19:03       ` Mathieu Segaud
2004-10-26 15:03     ` William Lee Irwin III
2004-10-26 21:19     ` Ed Tomlinson
2004-10-27  3:05       ` Marcos D. Marado Torres
2004-10-27  4:29         ` Rik van Riel
2004-10-27  5:13           ` Willy Tarreau
2004-10-27  5:23             ` William Lee Irwin III
2004-10-27  6:04               ` Willy Tarreau
2004-10-27  6:28                 ` William Lee Irwin III
2004-10-27  6:50                   ` Massimo Cetra
2004-10-27  6:56                     ` William Lee Irwin III
2004-11-16 16:43                     ` Bill Davidsen
2004-10-27 13:48               ` John Richard Moser
2004-10-27 14:57                 ` Theodore Ts'o
2004-10-27 15:35                   ` John Richard Moser
2004-10-27 19:46                     ` Marcos D. Marado Torres
2004-10-27 21:08                       ` John Richard Moser
2004-10-27 21:14                         ` Rik van Riel
2004-10-27 17:55                   ` William Lee Irwin III
2004-10-27 13:38             ` John Richard Moser
2004-10-27  5:25         ` John Richard Moser
2004-10-28  6:46           ` michael
2004-10-28  7:13             ` William Lee Irwin III
2004-10-28  7:28             ` Hacksaw
2004-10-29 21:30               ` Adrian Bunk
2004-10-28  7:57             ` Massimo Cetra
2004-10-28 16:14             ` John Richard Moser
2004-10-28 17:27               ` Theodore Ts'o
2004-10-28 23:19               ` michael
2004-10-29  0:02                 ` John Richard Moser
2004-10-27  4:26       ` Rik van Riel
2004-11-16 16:18       ` Bill Davidsen
2004-10-26 12:37   ` Barry K. Nathan
2004-10-26 14:40     ` Espen Fjellvær Olsen
2004-10-26 14:28   ` William Lee Irwin III
2004-10-26 14:41   ` Gene Heskett
2004-10-26 14:24 ` William Lee Irwin III
2004-10-27 15:27 ` Alan Cox
2004-10-26 15:54 Chuck Ebbert
2004-10-26 17:50 ` William Lee Irwin III
2004-10-26 16:32 Chuck Ebbert
2004-10-26 17:37 ` William Lee Irwin III
2004-10-27  0:00 Chuck Ebbert
2004-10-27  0:24 ` Dmitry Torokhov
2004-10-27  0:36   ` William Lee Irwin III
2004-10-27  0:36 ` William Lee Irwin III
2004-10-27  2:45   ` Marcos D. Marado Torres
2004-10-27  3:19     ` William Lee Irwin III
2004-10-27  2:47 ` Marcos D. Marado Torres
2004-10-27 19:50 Chuck Ebbert
2004-10-27 21:40 ` Alan Cox
2004-10-28  2:59   ` Dmitry Torokhov
2004-10-28 10:16     ` Alan Cox
2004-10-28 13:04 Chuck Ebbert
2004-10-28 13:15 ` Arjan van de Ven
2004-10-28 15:03 ` William Lee Irwin III
2004-10-28 15:07   ` William Lee Irwin III
2004-10-28 17:33   ` Alan Cox
2004-10-28 18:39     ` William Lee Irwin III
2004-10-29 13:19   ` Bill Davidsen
2004-10-29 17:49     ` William Lee Irwin III
2004-10-28 23:33 Chuck Ebbert
2004-10-28 23:53 ` William Lee Irwin III

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=20041023055212.GA21206@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=bunk@stusta.de \
    --cc=espenfjo@gmail.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 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.