All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Justin Wells <jread@semiotek.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please tag tested releases of the 2.4.x kernel
Date: Fri, 30 Nov 2001 16:28:48 -0800	[thread overview]
Message-ID: <20011130162848.I504@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011130220451.9D5AD38326@fever.semiotek.com>
In-Reply-To: <20011130220451.9D5AD38326@fever.semiotek.com>

On Fri, Nov 30, 2001 at 05:04:51PM -0500, Justin Wells wrote:
> 
> It would be great if on kernel.org there were a note indicating which 
> releases of the linux kernel had been favourably received. 
>
> If you could organize a bit you could even mark a release as "TESTED",
> or even "APPROVED". All it would mean is that after it had been out for
> a week or two nobody found any really serious problems.
>

Are you volunteering to keep up on which kernels had what erratas?

> "Really serious" would be something like it corrupts the filesystem, or
> crashes a lot, or fails to build, or introduces a remote root exploit.
> Releases like 2.4.14 (fails to build loopback) and 2.4.15 (corrupts) 
> would not be tagged as "APPROVED".
> 
> Also "APPROVED" or "TESTED" doesn't mean there are no issues or problems,
> just that they're the usual kind of issues and problems, rather than 
> really serious issues.
> 
> I expect there to be quite a bit of human judgement involved in applying
> the label. I'm not looking for a rigorous criteria--just the general 
> feeling of the community a week or two after the release was posted.
> 

The problem is that this is much like documentation.  It (should|needs to)
be done, but usually it'll be started, and then abandoned.

Something like LWN (Linux Weekly News) might be a good place for this.
Since you probably wouldn't want to know daily if you're going to be a few
versions behind.

mf

  parent reply	other threads:[~2001-12-01  0:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 22:04 Please tag tested releases of the 2.4.x kernel Justin Wells
2001-11-30 23:15 ` Mike Fedyk
2001-12-01  0:28 ` Mike Fedyk [this message]
2001-12-01  9:41 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2001-12-01  1:05 willy tarreau
2001-12-01  1:10 ` Mike Fedyk
2001-12-01  2:42   ` Ian Stirling
2001-12-01  2:53     ` Mike Fedyk
2001-12-01 11:31 ` Miquel van Smoorenburg
2001-12-02 23:38 Justin Wells

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=20011130162848.I504@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=jread@semiotek.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.