On Mon, May 26, 2003 at 11:04:42AM -0500, Luca - De Whiskey's - De Vitis wrote:
> On Mon, May 26, 2003 at 05:15:48PM +0200, Philipp Matthias Hahn wrote: > > Example: > > 1. detect bug > > 2. run reportbug > > 3. sees, other person was faster and reported bug 42. > > 4. wait for new version > > 5. read changlog > > 6. what the heck was bug 42, was it mine ? > > $ w3m http://bugs.debian.org/42 > I'm not so bothered by writing 32 characters to know what was it. > Off-line? Wait until on-line.. The bug report and the bug fix are separate things, and looking at the bug report often does not tell you how it was fixed. Changelog entries help users to deduce which package introduced a new bug, follow the history of a package to find out when a change was introduced. Looking back over a year's worth of versions by downloading bug reports from the BTS is not useful. A changelog entry which says only Closes: #<bug> is worthless; it is the same as leaving the changelog empty and closing the bug by hand. > Do you know how not to bother maintainers? Ask to the apt-listchanges > developers to add a feature to download bugs report for each bug closed in > changelog. This is not a bother to maintainers, and no amount of enhancement to apt-listchanges relieves the maintainer's responsibility to document his changes. -- - mdz
