[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080328203314.GC26555@elte.hu>
Date: Fri, 28 Mar 2008 21:33:14 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Adrian Bunk <bunk@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Pawel Staszewski <pstaszewski@...com.pl>,
Christoph Lameter <clameter@....com>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Natalie Protasevich <protasnb@...il.com>
Subject: Re: 2.6.25-rc7-git2: Reported regressions from 2.6.24
* Adrian Bunk <bunk@...nel.org> wrote:
> But that was one year ago when we had only half as many regressions
> per release as they do now, with 2.6.25 we had a peak of 66 pending
> regressions...
we have twice as many commits, and we have better test coverage. I get
the impression that user trust is coming back as well: regressions are
being reported sooner and more persistently - because we are handling
them in a more structured and more dependable way. We also seem to have
more users of latest -git.
so it _appears_ to be an increase in bugginess but i believe it's an
increase of activity and it's all good IMO, we close 90% of the
regressions within a week or two, and most of the regressions are for
obscure cases.
I had 2.6.25 running on most of my boxes from -rc1 on without any
unprovoked crash. (provoked bugs were another matter) Bisection became
more practical and more widespread as well. And i periodically find bugs
that came from ancient kernels so we are fixing bugs faster than we put
them in i think. I didnt have that feeling in the .18-.19 kernels.
also, now that the kerneloops.org client is in Fedora 9 by default,
we'll start to have really objective long-term statistics about how our
users react to the bugs we put into the kernel.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists