From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752618Ab2AWBHu (ORCPT ); Sun, 22 Jan 2012 20:07:50 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:45361 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752540Ab2AWBHt (ORCPT ); Sun, 22 Jan 2012 20:07:49 -0500 From: "Rafael J. Wysocki" To: David Miller Subject: Re: Regression tracking Date: Mon, 23 Jan 2012 01:52:25 +0100 User-Agent: KMail/1.13.6 (Linux/3.3.0-rc1+; KDE/4.6.0; x86_64; ; ) Cc: maciej.rutecki@gmail.com, davej@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <201201222031.51116.maciej.rutecki@gmail.com> <201201222052.02135.maciej.rutecki@gmail.com> <20120122.150707.1411449164435920150.davem@davemloft.net> In-Reply-To: <20120122.150707.1411449164435920150.davem@davemloft.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201230152.25575.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sunday, January 22, 2012, David Miller wrote: > From: Maciej Rutecki > 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