netdev - Re: Regression tracking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Jan 2012 01:52:25 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	David Miller <davem@...emloft.net>
Cc:	maciej.rutecki@...il.com, davej@...hat.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Regression tracking

On Sunday, January 22, 2012, David Miller wrote:
> From: Maciej Rutecki <maciej.rutecki@...il.com>
> Date: Sun, 22 Jan 2012 20:52:02 +0100
> 
> > OK. But tracking regressions in two (or more) places is nonsense. And this 
> > puts into question all of my current work, such as how to analyze 
> > (automatically) the progress of the whole kernel and its quality per each -rc. 
> > Problem to discussion, but if everyone will do as you wish, it will all work 
> > went to waste.
> 
> If someone else wants to maintain the state of bugs on some web
> site and click buttons all day long, that is their perogative.
> 
> But it's not something I'm going to do.
> 
> You can't force people to use tools, and frankly that's the end of
> this conversation as far as I'm concerned.

Well, people who are tracking regressions need to keep the record of
what's been reported etc. somewhere and we use the Bugzilla for this
purpose (basically, as a database).  I, personally, have never been
expecting developers to follow the entries put in there by us, unless
they want to, but then we'd like the _reporters_ to update the status
(resolved/closed) which saves us quite some time (e.g. if someone
closes a bug entry created for a regression reported by him, we don't
need to dig through the git history and mailing lists archives or ask
developers whether or not the given bug has been fixed).

I hope that clarifies things.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html