[5300] in Athena Bugs
rt 6.4R: the kernel
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed Jun 27 00:05:47 1990
Date: Wed, 27 Jun 90 00:05:22 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: marc@MIT.EDU
Cc: marc@ATHENA.MIT.EDU, bugs@ATHENA.MIT.EDU
In-Reply-To: bugs[5126]
From: marc@MIT.EDU
Reply-To: marc@MIT.EDU
Usmail: Marc Horowitz, 3 Ames Street, Cambridge, MA 02139
Phone: (617)225-6447
Date: Fri, 08 Jun 90 16:08:08 EDT
Can you explain what the software suggestion process is, and how it
works? I know it's there, but I don't know anything else about it.
1. User reports suggestion to software-suggestions.
2. Henry (or whoever is currently processing suggestions) filters out
obviously bogus suggestions, or things that are bug reports rather
than suggestions (those get forwarded to "bugs", consulting the
rest of Release Engineering if necessary. Most ideas make it
through this step.
3. The suggestion is posted to the suggest discuss meeting.
4. It is discussed there.
5. The Release Engineering periodically reviews the suggestions in the
discuss meeting, and decides simply whether or not it is feasible
to implement each one.
7. The release team for the next upcoming release decides which
suggestions it thinks should make it into the release.
8. Those suggestions are pursued, i.e. we try to find someone to
implement them.
P.S. Is there any reason not to record something as both a suggestion
and a bug?
Yes. It makes more paperwork for everybody, and clogs up both the
suggestion and bug processes, and makes our jobs more difficult.
If you report something as a bug and we think it's a suggestion, it'll
get moved to software-suggestions, and vice versa, so there's no
reason to report it as both a bug and a suggestion.
Jonathan Kamens
Project Athena Quality Assurance
