[1927] in Release_7.7_team
Re: How can we better acknowledge Athena bug reports?
daemon@ATHENA.MIT.EDU (t. belton)
Thu Sep 16 11:35:54 1999
Date: Thu, 16 Sep 1999 11:35:43 -0400 (EDT)
From: "t. belton" <tbelton@MIT.EDU>
To: Bill Cattey <wdc@MIT.EDU>
Cc: release-team@MIT.EDU
In-Reply-To: <Urs1k8gGgE6e1AZQk0@mit.edu>
Message-Id: <Pine.GSO.3.96L.990916113207.27363F-100000@iphigenia.mit.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Well, as noted, I always reply to bug-infoagents reports, or bug reports
that fall within the infoagents/netscape region. I also have taken to
forwarding Acrobat bug reports to Alex Prengel once I realized he would
otherwise have no way of seeing them.
I'm not sure that you're going to be able to talk the consultants into
taking on this duty, nor am I sure they should. Seems to me that the
person who's going to be fixing the bug should be the person who posts an
acknowledgement that we're looking into it. Suppose we tried to work out a
system where everyone took care of replies for bugs which were "theirs"?
Would there be enough consensus on who owns what code?
-Todd
On Wed, 15 Sep 1999, Bill Cattey wrote:
> Problem:
>
> Users who take the time to submit bug reports do not reliably get an
> acknowledgement of any kind. Although Mike Barker, and Greg Hudson on a
> best efforts basis reply to some of the incoming bug reports, there
> really is no guarantee that a bug report will be read or replied to.
>
> It occurs to me that, properly speaking, the task of saying "We received
> your report, and are sorry you were inconvenienced." is a SUPPORT issue.
> Is there some way we can get coverage here from consultants, or help
> desk personnel?
>
> -wdc
>
