From: Adrian Bunk <bunk@fs.tum.de>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.8-rc1
Date: Mon, 12 Jul 2004 17:42:04 +0200 [thread overview]
Message-ID: <20040712154204.GS4701@fs.tum.de> (raw)
In-Reply-To: <4d8e3fd3040712023469039826@mail.gmail.com>
On Mon, Jul 12, 2004 at 11:34:59AM +0200, Paolo Ciarrocchi wrote:
> On Sun, 11 Jul 2004 11:29:44 -0700 (PDT), Linus Torvalds
> <torvalds@osdl.org> wrote:
> >
> > Ok, there's been a long time between "public" releases, although the
> > automated BK snapshots have obviously been keeping people up-to-date.
> > Sorry about that, I blame mainly moving boxes and stuff around...
>
> Maybe I'm just missing the whole point but I wonder if we could define
> a series of 'test' a version should pass before being marked as -rc ir
> final.
>
> Now that we have the automated BK snapshots the "public" release seems
> to be a minor milestone in the process.
>
> I would like to see ltp test suite, OSDL's compile stats and OSDL
> benchmarking as part of the release process.
>
> Does it make sense ?
Unless he really knows what he's doing, no user should use anything
other than the actual releases (i.e. 2.6.7, 2.6.8, 2.6.9,...).
OSDL does some tests for any -rc and many other people like me do other
testing. Besides this, most patches already got similar treatment in
-mm. This might not be a base for an ISO 9000 certificate, but it seems
to be sufficietely working for finding most problems before the acttual
release.
It would be more important if Linus would release one last -rc that will
be released unchanged (except for EXTRAVERSION a few days later to catch
bugs in last minute changes. This might catch more problems like the JFS
compile problem in 2.6.7.
> Ciao,
> Paolo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-07-12 15:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 18:29 Linux 2.6.8-rc1 Linus Torvalds
2004-07-11 23:00 ` [PATCH] edd (Re: Linux 2.6.8-rc1) Randy.Dunlap
2004-07-12 3:02 ` Adrian Bunk
2004-07-12 4:49 ` Matt Domsch
2004-07-12 5:21 ` Randy.Dunlap
2004-07-12 9:26 ` Linux 2.6.8-rc1 Matthias Andree
2004-07-12 18:54 ` Martin Schlemmer
2004-07-12 9:34 ` Paolo Ciarrocchi
2004-07-12 15:42 ` Adrian Bunk [this message]
2004-07-12 15:56 ` Paolo Ciarrocchi
2004-07-12 16:34 ` Adrian Bunk
2004-07-12 16:43 ` Linus Torvalds
2004-07-12 20:28 ` Paolo Ciarrocchi
2004-07-12 20:22 ` Paolo Ciarrocchi
2004-07-13 20:54 ` cliff white
2004-07-12 21:08 ` Horst von Brand
2004-07-12 11:30 ` is_highmem() and WANT_PAGE_VIRTUAL (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 13:51 ` Andy Whitcroft
2004-07-12 14:23 ` Geert Uytterhoeven
2004-07-12 12:01 ` Linux 2.6.8-rc1 Geert Uytterhoeven
2004-07-12 13:18 ` OGAWA Hirofumi
2004-07-12 13:25 ` Geert Uytterhoeven
2004-07-12 14:02 ` OGAWA Hirofumi
2004-07-12 13:23 ` struct_cpy() and kAFS (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 18:11 ` Andrew Morton
2004-07-12 18:23 ` Christoph Hellwig
2004-07-12 18:40 ` Andrew Morton
2004-07-13 10:14 ` David Howells
2004-07-12 23:49 ` Linux 2.6.8-rc1 (compile stats) John Cherry
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=20040712154204.GS4701@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=torvalds@osdl.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