From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.devel Subject: Re: More Bug Stuff Date: Mon, 25 Mar 2002 00:21:30 -0800 Sender: guile-devel-admin@gnu.org Message-ID: References: <873cypn2a2.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> <87d6xtzhzv.fsf@zagadka.ping.de> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1017044865 2443 127.0.0.1 (25 Mar 2002 08:27:45 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 25 Mar 2002 08:27:45 +0000 (UTC) Cc: evan@glug.org, guile-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16pPpQ-0000dI-00 for ; Mon, 25 Mar 2002 09:27:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16pPor-0005YG-00; Mon, 25 Mar 2002 03:27:09 -0500 Original-Received: from ca-crlsbd-u3-c5c-122.crlsca.adelphia.net ([68.64.59.122] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16pPmM-0005TQ-00 for ; Mon, 25 Mar 2002 03:24:35 -0500 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16pPjO-0006vO-00; Mon, 25 Mar 2002 00:21:30 -0800 Original-To: mvo@zagadka.ping.de In-Reply-To: <87d6xtzhzv.fsf@zagadka.ping.de> (message from Marius Vollmer on 25 Mar 2002 00:03:00 +0100) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:188 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:188 From: Marius Vollmer Date: 25 Mar 2002 00:03:00 +0100 Are we talking about tasks here as well, in addition to bugs? For tasks, priority makes more sense. bugs can result in tasks (like fixing them), and not all tasks are bug-related. over time tasks that encounter bugs become bug-related. presumably people might think it's a good idea to scan the bug list to see which bugs relate to work in progress, and adding info to the bug db whenever something interesting occurs might help fix bugs faster, and DTRT. so to me these two areas can be better managed separately. bugs db should be descriptive and avoid being prescriptive. referring to a task from a bug header is already supported. task prioritization is undocumented mostly because everyone (human) is motivated differently when they look at any set of tasks. it is a personal matter which some may never be comfortable in disclosing. more basically, even knowing one's own motivations is difficult sometimes. probably we can come to rough consensus (as we go along, and enough to get stuff done) at which time someone should write tasks/TRIAGE. (a bugs/TRIAGE is a good idea too.) perhaps we can borrow further from debian. after some thought i believe one dir per bug is a better overall fit. sorry about being overhasty. every other approach invents weird syntax (like the one we're leaving) to forget and screw up. [jobs clones guffaw "bundles" into their grey cubes.] on the other hand, single file at top is simple and here. so really, my proposal (now -- please ignore previous) comes down to: N -- the rfc822 for bug N .N -- the directory w/ all of bug N's related files; may be empty or absent in the headers, this would add required header: bug-stuff-dir: .N under .N things can be named in regular ways, such as "test-case-1.scm" or "why-i-must-rant-against-this-bug" or "rfc822" (symlink). the naming of these files can be conventionalized later and w/o overmuch regard to the actual bug number. programs that munge these files are accordingly lightened. programs that munge bug sets need to stay informed w/ `bug-stuff-dir' but that's just another header (already done). thi _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel