public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: Re: Some thoughts about stable kernel development
Date: Mon, 10 Nov 2003 08:35:36 -0500	[thread overview]
Message-ID: <20031110133536.GA1780@ncsu.edu> (raw)
In-Reply-To: <m3u15de669.fsf@defiant.pm.waw.pl>

> There is a problem that a development cycle (time between stable
> = non-pre/rc versions) is long.

This sentiment is expressed fairly often, and I have never seen it challenged.
However, I am not convinced that it is true.  I do not believe that people
who care about stability want to upgrade to a new kernel with major changes
in it every 9 months.  It also takes a fairly long time for our "stable"
kernels to actually get stable enough that vendors are comfortable shipping
them.  I think if our develpment cycle gets significantly shorter, you will
end up with vendors skipping entire stable series (ie. moving from 2.2 to 2.6
without ever doing 2.4).  I think that would create more pain for us than our
current release cycle length does.

Thanks,

Jim

  parent reply	other threads:[~2003-11-10 13:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 18:41 Some thoughts about stable kernel development Krzysztof Halasa
2003-11-09 19:05 ` Valdis.Kletnieks
2003-11-12 15:05   ` Krzysztof Halasa
2003-11-09 19:06 ` Stefan Smietanowski
2003-11-12 15:07   ` Krzysztof Halasa
2003-11-12 16:04     ` Stefan Smietanowski
2003-11-12 16:51       ` Krzysztof Halasa
2003-11-13  7:33         ` Stefan Smietanowski
2003-11-13 19:55           ` Krzysztof Halasa
2003-11-09 19:26 ` Andrew Morton
2003-11-09 20:34   ` Alan Cox
2003-11-09 20:41   ` Maciej Zenczykowski
2003-11-09 19:29 ` Willy Tarreau
2003-11-12 15:01   ` Krzysztof Halasa
2003-11-09 19:50 ` John Bradford
2003-11-09 23:49   ` Valdis.Kletnieks
2003-11-10  8:53     ` John Bradford
2003-11-09 23:54   ` Rob Landley
2003-11-10  8:50     ` John Bradford
2003-11-11  7:47       ` Ryan Anderson
2003-11-11  8:19       ` Valdis.Kletnieks
2003-11-11  8:53         ` John Bradford
2003-11-10 10:58 ` Marcelo Tosatti
2003-11-12 14:48   ` Krzysztof Halasa
2003-11-10 13:35 ` jlnance [this message]
2003-11-12 14:43   ` Krzysztof Halasa
2003-11-10 16:54 ` Adrian Bunk
2003-11-12 14:40   ` Krzysztof Halasa
  -- strict thread matches above, loose matches on Subject: below --
2003-11-09 21:53 Matt

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=20031110133536.GA1780@ncsu.edu \
    --to=jlnance@unity.ncsu.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox