Re: Bug#123234: Deprecate BTS "close" command?
On Mon, 10 Dec 2001, Luca - De Whiskey's - De Vitis wrote:
> On Mon, Dec 10, 2001 at 12:54:43PM +0000, Mark Brown wrote:
> > You can still close bugs by mailing nnnnn-done@bugs.debian.org. The
> > problem with using closes rather than this is that the submitter just
> > gets notified that their bug has been closed with no explanation as to
> > why. If you mail -done a copy of the mail gets sent to the submitter,
> > hopefully explaining why the bug has been closed.
>
> Yes, I know, but with the two examples i reported a DD do not need to
> explain the reason: in the first case, the change-log file should list the
> changes and their reason;
Why wouldn't you want to tell a user the changes you made that fix your
bug?
If you close a bug, you *always* need to explain why *by mail*. Either by
letting katie do it (which is what happens if you close it through your
changelog) or by sending a separate mail.
> in the second case, the existence of the
> package is the reason.
> Sending an email to the submitter would be glad, sure, but would
> introduce redundancy of information, and would be quite annoying.
No, it would not. You cannot assume that everyone reads -changes or
-devel-changes or whatever list that particular packages' changelog
happens to appear on.
<snip>
--
wouter dot verhelst at advalvas dot be
"Human knowledge belongs to the world"
-- From the movie "Antitrust"
Reply to: