mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: c0330 <c0330@yingwa.edu.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Future of Kernel tree 2.0 ............
Date: Sun, 14 Jul 2002 01:37:01 +0200	[thread overview]
Message-ID: <20020713233701.GO29001@khan.acc.umu.se> (raw)
In-Reply-To: <E17TUXf-0000Ow-00@ited.yingwa.edu.hk>

On Sat, Jul 13, 2002 at 09:35:03PM +0000, c0330 wrote:
> Hi everbody,
> 
> Will kernel tree 2.0 stop developing and regard historical after the
> release of 2.6?  I think we would put our focus on much more newer
> kernel. And I found this may confuse the newbies, because they don't
> know much about versioning in Kernel.
> 
> In nowsdays, there are less less compputers using 2.0. We should
> push them to upgrade, so I think stop developing 2.0 is better, in
> my opinion

The developer-force going into the 2.0-series is not very big. I
consolidate the few fixes I get sent my way that are reasonable, and
reject the rest (lately, most have been reasonable...), and try to
backport some fixes from 2.2/2.4 that are applicable. No new drivers are
added (or developed), and no new features are added.

Besides me, there are a few (no more than five) persons that regularly
report their success/failure/personal gripes with the latest
2.0-releases, and remind me to increase the release-number (I'm as bad
as Alan in this regard...)

The amount of work that I'd spend on a newer kernel would be about the
same, and since I've grown fond of this work, I'll probably not drop
2.0 unless I get offered to take over 2.2 or 2.4 some point in the
future.

Mind you, there _are_ people that still use 2.0 and wouldn't consider an
upgrade the next few years, simply because they know that their
software/hardware works with 2.0 and have documented all quirks.
Upgrading to a newer kernel-series means going through this work again.
And most likely, the upgrade would be to 2.2 rather than 2.4, because
2.4 still gets new features and API-changes now and then, something
generally frowned upon in a controlled environment.

I am about to release 2.0.40 soon, and while 40 is a nice round number,
42 is an even better number to stop at, so that'll probably be the end
of the road. That end lies quite some time in the future, though.


Regards: David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  parent reply	other threads:[~2002-07-13 23:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13 21:35 c0330
2002-07-13 13:37 ` William Lee Irwin III
2002-07-13 13:41 ` Rik van Riel
2002-07-13 13:43 ` Roy Sigurd Karlsbakk
2002-07-13 16:07   ` Gerhard Mack
2002-07-13 17:11     ` Thunder from the hill
2002-07-14  0:42   ` Erik Andersen
2002-07-13 14:53 ` Alan Cox
2002-07-13 15:34   ` Stephen Frost
2002-07-13 15:36 ` Jose Luis Domingo Lopez
2002-07-13 16:28 ` Austin Gonyou
2002-07-13 23:49   ` David Weinehall
2002-07-15  4:07     ` Austin Gonyou
2002-07-15 19:22     ` Bill Davidsen
2002-07-15 19:42       ` Jeff Dike
2002-07-13 23:37 ` David Weinehall [this message]
2002-07-15  2:16   ` Eric W. Biederman

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=20020713233701.GO29001@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=c0330@yingwa.edu.hk \
    --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

all inboxes | Powered by JetHome®