[153] in Athena User Interface
Re: bug tracking for aui
daemon@ATHENA.MIT.EDU (Richard Tibbetts)
Thu Jun 8 12:26:37 2000
Message-Id: <200006081621.MAA02682@hikari-no-ken.mit.edu>
To: Brad Thompson <yak@MIT.EDU>
cc: Greg Hudson <ghudson@MIT.EDU>, aui@MIT.EDU, zacheiss@MIT.EDU,
tibbetts@MIT.EDU
In-reply-to: Your message of "Thu, 08 Jun 2000 11:50:07 EDT."
<200006081550.LAA00524@manatee.mit.edu>
Date: Thu, 08 Jun 2000 12:21:19 -0400
From: Richard Tibbetts <tibbetts@MIT.EDU>
On 6/8 you wrote:
> > This seems very error-prone. Creating an aui-bugs list/meeting and
> > flagging resolved bugs is probably better.
>
> That works, too. Just as long as we have _something_.
> We need it soon, because right now we are tracking bugs in our
> heads and propagating bug-fix notices by rumor.
Because discuss does not have threading, I think that this is still
sub optimal. Suggestion:
1) Put the notebook in CVS with a new list (ala aui-diffs) that gets
sent mail about changes. Possibly this "new list" should just be
aui@mit.edu.
2) Make a new file there, bugs.html. Define a decent format for it and
make it editable with a text editor. Thwap Beland if he tries to
test an HTML editor on it.
This way it doesn't require much effort for the mundanes to check if
their bug has been reported. We can also store more interesteding
data, like "yak is working on this one" or "this bug will be fixed in
2.0, we hope" which would not fit into discuss well.
The downside is that registering a bug requires access to the
repository (or at least part of it).
Do people think this is a bad idea? I will be in the Zone in an hour
or two if people want to talk about it in person.
tibbetts
-*- http://www.mit.edu/~tibbetts -*- finger tibbetts@monk.mit.edu -*-
