mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Oosthoek <simon@margo.student.utwente.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x release process comments
Date: Thu, 20 Feb 2003 13:58:08 +0100	[thread overview]
Message-ID: <20030220125808.GA11694@margo.student.utwente.nl> (raw)
In-Reply-To: <200302201056.h1KAuwui000635@81-2-122-30.bradfords.org.uk>

On Thu, Feb 20, 2003 at 10:56:58AM +0000, John Bradford wrote:
> > - Kernel version releases (and -pre releases) do not happen often enough to
> > keep up with recent hardware
> > 
> Distributions typically use modified versions of the standard kernel
> anyway.  The kernel development schedule has never been based around
> the needs of any particular distribution or distributions.

I'm not saying it should, but it would be good from a PR perspective and as
an element in the reliability feeling vector ;-)
 
> > I'd love to see regular (say once a week) releases -preX releases and no
> > more than 10 -pre releases before a -rc. No more than 4 -rc's (released no
> > more than 2 weeks apart) before a new version. Faster full version releases
> > would also be fine with me.
> 
> It doesn't make sense to limit the number of -pre releases and release
> candidates - they are needed to make sure, as far as possible, that
> the actual release is stable.

The number of -pre releases shouldn't be limited for its own sake, but
rather in the process of stabilising the kernel for release. So I mean after
a couple of -pre releases start focussing on debugging and then finish with
a few -rc's before the next cycle starts. That way the diffs between full
versions are smaller and upgrading gets easier.
 
> > My personal interest in this is that my laptop is not yet working 100%...
> > (see http://margo.student.utwente.nl/simon/ongoing/jade8060.php)
> 
> I had a quick look, and it looks like it's 95% working, though :-).

yup, I'm getting there :-) Would be nice to have the smartcard reader
working as well... Some things I can't test because I don't have the
hardware (IEEE1394, wireless lan, irda). power management is still quite
magical to me though ;-)

Cheers

Simon

  reply	other threads:[~2003-02-20 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 10:24 Simon Oosthoek
2003-02-20 10:56 ` John Bradford
2003-02-20 12:58   ` Simon Oosthoek [this message]
2003-02-20 13:11     ` Paul Rolland
2003-02-20 13:24       ` Simon Oosthoek
2003-02-20 14:51 ` Alan Cox

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=20030220125808.GA11694@margo.student.utwente.nl \
    --to=simon@margo.student.utwente.nl \
    --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®