From owner-freebsd-bugs Mon May 4 15:52:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20954 for freebsd-bugs-outgoing; Mon, 4 May 1998 15:52:51 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20939 for ; Mon, 4 May 1998 15:52:48 -0700 (PDT) (envelope-from woods@tap.zeus.leitch.com) Received: from zeus.leitch.com (tap.zeus.leitch.com [204.187.61.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id SAA03004; Mon, 4 May 1998 18:53:02 -0400 (EDT) Received: from brain.zeus.leitch.com (brain.zeus.leitch.com [204.187.61.32]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id SAA25105; Mon, 4 May 1998 18:53:09 -0400 (EDT) Received: (from woods@localhost) by brain.zeus.leitch.com (8.8.8/8.8.8) id SAA21201; Mon, 4 May 1998 18:53:09 -0400 (EDT) (envelope-from woods@tap.zeus.leitch.com) Date: Mon, 4 May 1998 18:53:09 -0400 (EDT) Message-Id: <199805042253.SAA21201@brain.zeus.leitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@zeus.leitch.com (Greg A. Woods) To: "Jordan K. Hubbard" Cc: Randall Hopper , Poul-Henning Kamp , freebsd-bugs@FreeBSD.ORG Subject: Re: bin/5296 In-Reply-To: Jordan K. Hubbard's message of "Mon, May 4, 1998 13:19:31 -0700" regarding "Re: bin/5296 " id <6821.894313171@time.cdrom.com> References: <199805041546.LAA16661@brain.zeus.leitch.com> <6821.894313171@time.cdrom.com> X-Mailer: VM 6.45 under Emacs 20.2.1 Reply-To: woods@zeus.leitch.com (Greg A. Woods) Organization: Planix, Inc.; Toronto, Ontario; Canada Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Mon, May 4, 1998 at 13:19:31 (-0700), Jordan K. Hubbard wrote: ] > Subject: Re: bin/5296 > > You've missed the point - it has nothing to do with hardware > limitations and much more to do with the fact that GNATs is just > basically unwieldy at handling this many. It may have a wonderful > priority matrix, but actually searching through and locating such PRs > is a real pain. I didn't think hardware or other system resources was the problem. In that case I'm not sure why you're finding it a "real pain" to search and locate "such" PRs. The current WWW summary report is indeed practically useless (except as a large and searchable summary report, assuming the synopsis text is meaningful), and the "formulate a specific query" page (which can only be linked to from the summary report and not from the "Support" page) doesn't sort by priority or severity, but anyone with direct GNATS access should be able to use either the query-pr command-line, or whatever front-end, to generate a very selective set of PRs. No matter what system you find, effective use of it in face of such a large user-base and potentially large number of submissions will require that you have energetic, knowledgeable, and dedicated people like phk to read through all submissions and re-file them with appropriate adjustments to the priority, severity, and/or class fields. I think a full-text search capability for PRs would help reduce the number of duplicates too. (glimpse and the WWW tools available for it should do fine, though the doing the right interface would probably take some development effort -- simple grep searches would probably require too much horsepower) > > In addition I hope it isn't necessary to point out that GNATS is free > > software and is in fact quite easy to modify and/or extend. It's not > > Easy when you have the time and resources, sure. :( Wouldn't it be more effective to enhance GNATS to the state where it is usable for your requirements rather than first finding (or worse designing and implmenting) some other tracking system (even if it's simply a separate GNATS database) and then moving all the "low-priority" PRs over to that new system? (Assuming it's GNATS that actually need enhancing, and not just its pattern of usage....) As you suggested in jest earlier, the only alternative is to wipe the slate clean and start fresh with new rules, systems, or whatever, and I think we all agree, esp. the collective group of submitters, that this is just not a viable alternative at this stage. -- Greg A. Woods +1 416 443-1734 VE3TCP Planix, Inc. ; Secrets of the Weird To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message