Re: changelog bug-closing should not be used unless the code changes
On Tue, 2 Jan 2001, Joey Hess wrote:
> Bugs don't expire from the BTS.
>
> I dislike the practice myself. If my bug's being closed out of hand, a
> personal email makes it feel a little less cold. (On the other hand if
> my bug was fixed, I don't mind wading through the changelog to find
> that..)
I disagree with an entry of "Bugs closes previously: CLoses: #nnnnn". It
gives no indication of when, how, or why a bug was fixed. When I was going
thru the dpkg bug list, I sent lots of emails of the form: "This was fixed in
dpkg x.x.x". If I was bored, I included the time the version was uploaded.
It's not that much more difficult to send individual emails, then it is to
write an entry in a changelog. And it is much more friendly.
----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-----END GEEK CODE BLOCK-----
----BEGIN PGP INFO----
Adam Heath <doogie@debian.org> Finger Print | KeyID
67 01 42 93 CA 37 FB 1E 63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----
Reply to: