From: Evan Prodromou <evan@glug.org>
Cc: guile-devel@gnu.org
Subject: Re: More Bug Stuff
Date: Thu, 28 Mar 2002 10:52:45 -0600 [thread overview]
Message-ID: <871ye4y6qq.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (raw)
In-Reply-To: <87d6xtzhzv.fsf@zagadka.ping.de> (Marius Vollmer's message of "25 Mar 2002 00:03:00 +0100")
>>>>> "MV" == Marius Vollmer <mvo@zagadka.ping.de> writes:
MV> Do we need a number? I'd rather go with a symbolic name.
MV> Numbers are so, umm, 'C'.
It's much easier to auto-generate a unique number than a meaningful
unique symbolic name.
MV> Why "Title"? I prefer "Summary" for this.
Why worry about header names? "Summary" is fine.
Me> Name and email address of person who reported the bug, in
Me> angle-bracket format.
MV> Do we need to restrict us to the angle bracket format? What
MV> about allowing any RFC2822 mailbox?
It makes writing parsers easier. Do you really need the flexibility of
using ANY kind of address header?
>> All dates must either be in the above "standard" format, or in
>> the format:
>>
>> dd Mon YYYY
MV> I'd rather use the ISO format YYYY-MM-DD here. Do we need a
MV> time?
Fine. No, I don't think we particularly need a time.
>> * Priority (0,Inf)
MV> Again, do we need hard numbers for this? In general, I think
MV> it will be mostly arbitrary what priority number is assigned
MV> to a bug.
It makes it much easier to say things like this: "For the next beta,
we will fix all priority 1 bugs and as many 2 and 3 bugs as we can."
It makes it easier to mentally categorize that 1 bugs are more
important than 8 bugs. Also, it makes it clear that Priority and
Severity are two different things.
I'm a little confused why you say that priority assignment is "mostly
arbitrary". First off, you've set yourself up as the arbitrator, so
that's about right. But I think it's a generally common practice to
prioritize jobs to do with a number between 1 and N, where N is a
small integer. It's entirely subjective -- based on the project's
goals, not on any algorithmically derivable formula.
MV> Identifying critical bugs, and distinguishing bugs
MV> from wishlist items is important, tho. We can use Severity
MV> for this.
Hurgh. I knew this would come up. Did you read what I wrote about
Severity vs. Priority?
Me> NOTE that Priority and Severity are loosely coupled -- things
Me> that are more severe usually will have a high priority, but not
Me> necessarily. For example, updating the version string for a
Me> release is a high priority task, but it's not particularly
Me> severe (it'd be a nuisance).
MV> Are we talking about tasks here as well, in addition to bugs?
MV> For tasks, priority makes more sense.
Sorry, I mistakenly used the word "task" here, which seems to have
confused you. What I should have said was "piece of work." If a
release went out with the FSF address misspelled, this would be a low
_severity_ bug, but a high _priority_ one.
Anyways, OK, the rest looks good.
~ESP
--
Evan Prodromou
evan@glug.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-28 16:52 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
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 [this message]
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=871ye4y6qq.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us \
--to=evan@glug.org \
--cc=guile-devel@gnu.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).