Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 15 Nov 2002 05:52:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 15 Nov 2002 05:52:51 -0500 Received: from smtp.comcast.net ([24.153.64.2]:42994 "EHLO smtp.comcast.net") by vger.kernel.org with ESMTP id ; Fri, 15 Nov 2002 05:52:49 -0500 Date: Fri, 15 Nov 2002 05:58:27 -0500 From: FZiegler Subject: Re: Bugzilla bug tracking database for 2.5 now available. In-reply-to: To: linux-kernel@vger.kernel.org Message-id: <3DD4D353.5000500@mac.com> Organization: none MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021107 References: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1773 Lines: 45 Eric Northup wrote: >>things in major trees like -mm, >>-ac, -dj etc are likely going to end up in mainline sooner or later >>anyway ... wouldn't you rather know of the breakage sooner rather >>than later? > > > Would this be an appropriate use of the "version" tag in Bugzilla? Currently > the only choice is "2.5", but if that were renamed to "2.5-linus", then the > other heavily used patchsets could be monitored while making it easy for > people who only want to see bugs in Linus' tree. Analogous though slightly different suggestion: have a "Tree" column just where Mozilla have their (quite analogous) "OpSys" field. Compare http://bugme.osdl.org/queryhelp.cgi#bugsettings http://bugzilla.mozilla.org/queryhelp.cgi#bugsettings This way people can set their queries, and triagers manage triage, in such a way that nothing shows on anyone's radar until it's actually relevant to them. (Whether a tree appears in the list would be up to its maintainer, I guess.) Caveat: although *queries* for (say) "-ac OR -dj" are possible, the fields themselves are still single-valued. So there ought to be an agreement that a bug doesn't get promoted to "All" trees just because it's been confirmed on more than one. (This has been a recurring problem in Mozilla -- e.g. people have tended to flag PPC bugs against "All" OSes when they only meant Apple OSes, not NetBSD or Linux PPC. Multi-valuedness would be the clean solution but unfortunately, afaik, Bugzilla doesn't support it for those fields.) - 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/