Re: Bug#123234: Deprecate BTS "close" command?
Luca - De Whiskey's - De Vitis wrote:
> But as i stated in another email, any user can get the package source an
> check the changelog. I only do not suppose any one is interested in the
> way a bug is closed. For examples, when i file a bug, the only thing i
> would like to see is the bug closed: I'm not interested in the way it was
> closed (in most cases).
Some users are running stable and do not have apt configured to
download source packages from unstable, if they even know the fix went
into unstable.
Some users have limited bandwidth.
Some users whould not know how to unpack a source package if they had
one, or how to find the debian changelog.
Some users, when they receive a mail stating "This bug has been
closed by a Debian developer, who will email you with specifics in
due course" might expect the developer to follow through with the
promised mail, and be disappointed/confused/annoyed when it never
arrives.
Some users file bug reports because they have real issues affecting
their systems. As such, they don't just want to know that a bug is
closed, they want to know where they can get a fix from. Nothing in the
mail generated by the close command tells them that. Whenever I close a
bug report by hand I am sure to either tell the bug submitter (via
xxx-done) the version of the package that fixes the bug report, or tell
them why it's not a bug.
--
see shy jo
Reply to: