Re: don't close bugs without an explanation!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brian Nelson wrote:
|>
|>Fix the changelog in your local tree so that it properly documents the
|>real history of the package, but there's no need to upload until
|>something more important comes up.
|
|
| So then the bug submitters never see the real reason the bug was closed,
| apt-listchanges (presumably) suppresses the additions to the old
| changelog entry so that anyone with the package installed never sees the
| real entries... Plus, any maintainer clueless enough to write awful
| changelog entries is very likely a negligent maintainer, and thus highly
| unlikely to make an upload to fix "something more important" for many
| months. Why is this an OK situation? Is this to work around gimped
| architectures with broken autobuilders?
|
I totally agree. Besides this, the changelog is a part of the package
and not a less important one than for example a README or something like
this. I have actually seen uploads fixing one stupid typo in
documentation. I think it's preferable if changelogs are fixed immediately.
best regards,
david
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBVtzkdhEvvPyx3SMRAvDqAKCAy2MLSsDZlpqhv1r6xxclh1vwZwCfUflG
txcEPV6y6dTc87ZP/B8PKoc=
=yvyq
-----END PGP SIGNATURE-----
Reply to: