From: Svein Erik Brostigen <svein.brostigen@oracle.com>
To: Allan Sandfeld <linux@sneulv.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Release Policy [was: Linux 2.4.16 ]
Date: Tue, 27 Nov 2001 04:08:06 -0500 [thread overview]
Message-ID: <3C0357F6.4000300@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111261216500.88-100000@rc.priv.hereintown.net> <20011126161802.A8398@xi.linuxpower.cx> <3C034889.6040000@oracle.com> <E168dbm-0000Jr-00@Princess>
Allan Sandfeld wrote:
>On Tuesday 27 November 2001 09:02, Svein Erik Brostigen wrote:
>
>>What really scares me is not so much the way the kernels are numbered as
>>the way features gets added to
>>the kernels.
>>
>The problem is that for kernels new features _are_ bug-fixes. Like the new
>vm, work-around for discovered bugs in hardware, etc., etc.
>I an way what should't be done in a -rc release is new fixing features, but
>only the fixing _of_ features. ;-)
>
Hmmm... workarounds are not new features, but bug-fixes ;-)
The new vm is not a *new* feature, it is just a different vm than the
old. Even if you treat it as a new
feature, it should then be incorporated into a new-feature release, i.e
not in a 2.4.10.4, but maybe in what
would have been a 2.4.11.0.
I'm not going to be anal about this, but a more structured way of
handling new features/bug-fixes and release
numbering would be nice. A lot easier to know what you are programming
against and what you are
installing/testing.
--
Regards
Svein Erik
I've given up reading books; I find it takes my mind off myself.
_____________________________________________________________
Svein Erik Brostigen e-mail: svein.brostigen@oracle.com
Senior Technical Analyst Phone: 407.458.7168
EBC - Extended Business Critical
Oracle Support Services
5955 T.G. Lee Blvd
Orlando FL, 32822
Enabling the Information Age Through Internet Computing
_____________________________________________________________
The statements and opinions expressed here are my own and
do not necessarily represent those of Oracle Corporation.
next prev parent reply other threads:[~2001-11-27 9:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0111261003070.13400-100000@freak.distro.cone ctiva>
2001-11-26 16:38 ` Release Policy [was: Linux 2.4.16 ] David Relson
2001-11-26 15:33 ` Marcelo Tosatti
2001-11-26 17:14 ` David Relson
2001-11-26 21:15 ` Bill Davidsen
2001-11-26 17:22 ` Chris Meadors
2001-11-26 15:54 ` Marcelo Tosatti
2001-11-26 17:41 ` David Rees
2001-11-26 18:12 ` H. Peter Anvin
2001-11-26 18:29 ` David Weinehall
2001-11-26 18:31 ` H. Peter Anvin
2001-11-26 17:25 ` Marcelo Tosatti
2001-11-26 18:49 ` H. Peter Anvin
2001-11-26 19:00 ` François Cami
2001-11-26 19:06 ` Jonathan Lundell
2001-11-26 19:28 ` Flavio Stanchina
2001-11-26 19:43 ` Jonathan Lundell
2001-11-26 19:36 ` David Weinehall
2001-11-26 20:39 ` junio
2001-11-26 20:55 ` David Weinehall
2001-11-26 20:59 ` H. Peter Anvin
2001-11-26 21:18 ` Gregory Maxwell
2001-11-27 8:02 ` Svein Erik Brostigen
2001-11-27 8:28 ` Allan Sandfeld
2001-11-27 9:08 ` Svein Erik Brostigen [this message]
2001-11-27 10:07 ` Alex Bligh - linux-kernel
2001-11-27 14:43 ` Sven Vermeulen
2001-11-27 15:01 ` Ian Molton
2001-11-27 15:42 ` John Alvord
2001-11-27 16:03 ` Michel Angelo da Silva Pereira
2001-11-26 18:48 ` Bjoern A. Zeeb
2001-11-26 23:15 ` J.A. Magallon
2001-11-27 1:04 ` Andrew Morton
2001-11-27 1:13 ` Release Policy David S. Miller
2001-11-27 1:32 ` H. Peter Anvin
2001-11-27 7:39 ` Anuradha Ratnaweera
2001-11-27 7:40 ` H. Peter Anvin
2001-11-27 7:53 ` Anuradha Ratnaweera
2001-11-27 10:08 ` Harald Arnesen
2001-11-27 10:29 ` Keith Owens
2001-11-27 19:45 ` Mike Fedyk
2001-12-05 14:27 ` Jes Sorensen
2001-11-26 17:52 Release Policy [was: Linux 2.4.16 ] Dana Lacoste
2001-11-26 17:59 ` John Jasen
2001-11-27 7:41 ` Anuradha Ratnaweera
2001-11-27 20:16 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 12:54 Per-Olof Pettersson
2001-11-28 12:57 Per-Olof Pettersson
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=3C0357F6.4000300@oracle.com \
--to=svein.brostigen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sneulv.dk \
/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.