mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	florian@mickler.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Tracking regressions for next release(s)
Date: Mon, 26 Mar 2012 18:47:17 +0200	[thread overview]
Message-ID: <201203261847.17521.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <20120323101431.GA8832@liondog.tnic>

Hi,

On piątek, 23 marca 2012 o 11:14:31 Borislav Petkov wrote:
> On Fri, Mar 23, 2012 at 07:01:19AM +0100, Maciej Rutecki wrote:
> > I am interested in the opinion of the developers, testers, and
> > everyone involved in the development of the kernel, if they thing that
> > tracking regressions and monitoring the quality makes sense,
> 
> Absolutely.
> 
> > especially since I met several times (put it mildly) dislike of such
> > work and the bugs are repaired relatively slowly.
> 
> I can imagine people getting cranky when someone points out that there's
> a "boring" bug they need to fix instead of them working on the cool new
> feature they have thought of. It is the same old story we've been having
> since forever: people don't really love to fix bugs, especially if the
> code works for them and the bug doesn't appear on their boxes.
> 
> > Perhaps someone has comments or proposals for change (in the way of
> > work or me).
> 
> Yeah, we need a big bad assh*le :) who screams at everyone until their
> bugs is fixed.
> 
> But serioulsy, this hasn't changed: we definitely need a regression
> list, I think it works even better when Linus goes over it and says
> this is fixed, that is this commit, etc. because he pulls all the trees
> in the end, ... so yeah, I think what you guys are doing is good and
> important.
> 
> It would be even cooler if this list be expanded also to regressions in
> kernel performance which people have noticed from running benchmarks on
> different -rcs and have noticed differences there, maybe a website (not
> bugzilla) which lists all those regressions for interested parties to
> fix in addition to the LKML mails..., etc...
> 
> Thanks for your hard work, btw.


Borislav,  Bjorn Helgaas: thank you for the answer, but observing the 
reactions I get the impression that tracking the regression is not likely 
anyone's interest. In addition - especially on the last release cycle - 
sometimes encountered difficulties in cooperation on this topic with developers: 
ignoring request to update the status of the regression, or even add your e-
mail to bugzilla.

I give up tracking the regression, but not the kernel testing. Even now I have 
a few hours per week more for it.

Regards
-- 
Maciej Rutecki
http://www.mrutecki.pl

  reply	other threads:[~2012-03-26 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  6:01 Maciej Rutecki
2012-03-23 10:14 ` Borislav Petkov
2012-03-26 16:47   ` Maciej Rutecki [this message]
2012-03-26 18:58     ` Borislav Petkov
2012-03-26 20:01       ` H. Peter Anvin
2012-03-23 15:58 ` Bjorn Helgaas

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=201203261847.17521.maciej.rutecki@gmail.com \
    --to=maciej.rutecki@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=florian@mickler.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

Powered by JetHome