Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 17 Oct 2002 20:04:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 17 Oct 2002 20:04:54 -0400 Received: from franka.aracnet.com ([216.99.193.44]:60110 "EHLO franka.aracnet.com") by vger.kernel.org with ESMTP id ; Thu, 17 Oct 2002 20:04:52 -0400 Date: Thu, 17 Oct 2002 17:08:19 -0700 From: "Martin J. Bligh" Reply-To: "Martin J. Bligh" To: Zwane Mwaikambo cc: Greg KH , linux-kernel Subject: Re: Bug tracking in the run up from 2.5 to 2.6 Message-ID: <2263066918.1034874498@[10.10.2.3]> In-Reply-To: References: X-Mailer: Mulberry/2.1.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 24 >> > If there are people to do the categorizing and "cleaning" of the >> > reported bugs, I would love to use this. By "cleaning" I mean the >> > following at the minimum: >> > - marking bugs as duplicates of existing bugs >> > - throwing away useless bug reports > > Sounds great, how do we handle duplicate work? ie will there be bug > assignments ? Obvious duplicates will be filtered out by the general admins. More subtle type things will probably need to be by the "owners" of the bugs, ie yes ... we'll have some sort of assingment of bugs. Ideally I'd like this to just be the subsystem maintainers as we have them now, but if they don't want to play, we'll find someone to act as administrative owner for each technical area that has experience in that field. Martin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/