[649] in Athena Bugs
How to write a bug report
daemon@ATHENA.MIT.EDU (Henry Mensch)
Fri Aug 26 00:29:04 1988
To: rt-testers@ATHENA.MIT.EDU, vs-testers@ATHENA.MIT.EDU,
Cc: bugs@ATHENA.MIT.EDU
Date: Fri, 26 Aug 88 00:28:22 EDT
From: Henry Mensch <henry@ATHENA.MIT.EDU>
I put this together some time ago when a particular user was
submitting bug reports with not-quite-enough information. As I only
see bits and pieces of this implemented in the bug reports I see, I
thought it would be useful to broadcast this. If I've missed
anything, I'm sure you'll let me know.
First, you should include a "Subject:" line. On that subject line
should be the software release you are using (e.g., RT 5.5T, VS 6.0,
etc.), and a short description of the bug you are reporting:
Subject: VS 5.3: zwrite doesn't always send a message
Some of the programs we use to track these things (discuss, notes,
etc.) display the "Subject:" field as part of an index, so this will
help us keep track of what's been reported.
In the text of the bug report you should specify the CPU type (VS II
or VS2000, RT or APC/RT). You should also say what's wrong, what you
think should have happened; also, please show an example or two of
what you did and how the system responded to your commands. If you
noticed this problem on a workstation in a private cluster, you should
state this fact in your message.
In collecting your example, you can use the X cut-and-paste facility
to make this easier, or you can turn on logging in the X window
(logging saves your commands in a file; it's much easier to use than
script. Just bring up a menu with Control-left-mouse-button and
select "logging.").
If you have any questions about this, please let me know.
Thanks,
-- Henry Mensch / <henry@ATHENA.MIT.EDU>
-- Project Athena Quality Assurance
