RANT: Re: Bug#123234: Deprecate BTS "close" command?
Note: my rant below is not directed at Colin.
On Mon, 10 Dec 2001, Colin Watson wrote:
> Mail the changelog to email@example.com. Please. Otherwise the
> submitter has to go hunting around for a changelog they often won't even
> have installed locally to find out why their bug was closed. This is
This assumes developers can write changelogs. An entry of:
* Closes: #123456, #55667.
is not an entry that should be used. It gives <bold><blink><flash><sound>NO
</sound></flash></blink></bold> information. Also:
* Applied patch from BTS: Closes: #99887.
is really not valid either. I should be able to know what the bug is about,
and why it was closed, by JUST reading the changelog entry.
Generally, when bugs of mine(or bugs that I have participated in) are closed
in such a fashion, I reopen then, demanding a proper entry in the bug log.
> The alternative, of course, is to cause mails to control@ to be copied
> to the submitter.
This is what I suggested in another email.