From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: evan@glug.org, guile-devel@gnu.org
Subject: Re: More Bug Stuff
Date: Mon, 25 Mar 2002 00:21:30 -0800 [thread overview]
Message-ID: <E16pPjO-0006vO-00@giblet> (raw)
In-Reply-To: <87d6xtzhzv.fsf@zagadka.ping.de> (message from Marius Vollmer on 25 Mar 2002 00:03:00 +0100)
From: Marius Vollmer <mvo@zagadka.ping.de>
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
next prev parent reply other threads:[~2002-03-25 8:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 20:23 More Bug Stuff Evan Prodromou
2002-03-24 23:03 ` Marius Vollmer
2002-03-25 8:21 ` Thien-Thi Nguyen [this message]
2002-03-25 15:48 ` Rob Browning
2002-03-25 21:19 ` Thien-Thi Nguyen
2002-03-25 21:35 ` Marius Vollmer
2002-03-25 22:00 ` Thien-Thi Nguyen
2002-03-25 22:03 ` Thien-Thi Nguyen
2002-03-25 22:25 ` Marius Vollmer
2002-03-27 0:31 ` Evan Prodromou
2002-03-27 2:58 ` Thien-Thi Nguyen
2002-03-27 19:09 ` Marius Vollmer
2002-03-27 20:39 ` Thien-Thi Nguyen
2002-04-07 11:17 ` Marius Vollmer
2002-04-07 19:05 ` Thien-Thi Nguyen
2002-04-07 21:22 ` Thien-Thi Nguyen
2002-04-07 21:38 ` Marius Vollmer
2002-03-27 18:56 ` Marius Vollmer
2002-03-28 16:52 ` Evan Prodromou
2002-03-29 4:02 ` Thien-Thi Nguyen
2002-04-07 12:03 ` Marius Vollmer
2002-04-07 22:22 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16pPjO-0006vO-00@giblet \
--to=ttn@giblet.glug.org \
--cc=evan@glug.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).