All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: A users thoughts on the new dev. model
Date: Tue, 27 Jul 2004 16:20:35 -0400	[thread overview]
Message-ID: <ce6cur$i2m$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20040722155759.0299dbc7.pj@sgi.com>

Paul Jackson wrote:
> Evan,
> 
> Have you found (1) Linus' 2.6 bk tree to meet your needs over the last
> few months?  Or (2) has it been too unstable for you?
> 
> If (1), seems like you might be in good shape, as from what I can
> gather of this (not being in Ottawa) next month looks alot like
> last month, so far as how Linux is developed.
> 
> If (2), then perhaps there is an opportunity here for a derivative of
> Linus' tree that is "stabilized a bit", but not overly patched like
> certain vendor kernels I won't name.
> 
> Yes, we'd all like the head kernel to march to the beat of our
> particular needs, rapidly changing and adding what we need without
> delay, leaving the rest untouched, and never breaking.
> 
> Now ... back to reality ...
> 
I'm not sure that's true, I personally think there is a lot to be said 
about the model currently being used for 2.2 and 2.4, which is almost 
totally bug-fix mode. Is that bad? The addition of minor fixes, like 
better scheduling, should not impact stability, let more massive changes 
(and feature deletions) be omitted. Is a new Reiser version likely to be 
more stable than what we have, or should this wait for a development 
version? Good, put it somewhere else.

I like to invert the arguments for putting new stuff in 2.6, let's go 
back to the excitement of development and open 2.7, and put 2.6 out to 
pasture right away. Then 2.6 can really be stable and 2.7 can go hog 
wild, without holding back the developers with pesky users.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2004-07-27 20:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 15:04 A users thoughts on the new dev. model Evan Hisey
2004-07-22 22:25 ` Bill Davidsen
2004-07-23 13:58   ` H. Peter Anvin
2004-07-23 15:24     ` szonyi calin
2004-07-23 16:39       ` David Ford
2004-07-23 19:06         ` Xiong Jiang
2004-07-23 20:00           ` Tim Wright
2004-07-23 21:40     ` Adrian Bunk
2004-07-23 23:04       ` hpa
2004-07-24 10:38         ` Adrian Bunk
2004-07-27 20:08       ` Bill Davidsen
2004-07-22 22:57 ` Paul Jackson
2004-07-27 20:20   ` Bill Davidsen [this message]
2004-07-28  7:31     ` Paul Jackson
2004-07-23 19:32 ` Florin Andrei

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='ce6cur$i2m$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.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.