Re: keeping a fixed bug fixed (was Re: proving a bug is gone)
On 09-Nov-98, 11:07 (CST), Daniel Martin <dtm12@jhunix.hcf.jhu.edu> wrote:
> I will repeat my suggestion (since when I first made it, it was in a
> parenthetical comment and I wasn't quite certain what I meant by it
> anyway) for a "List of fixed bugs" to be included either under
> /usr/doc/<package>/ or at the very least in the debian/ subdirectory
> of the source package.
>
> There could be a somewhat standardized format, as there is with the
> changelog, describing in a few sentences (?) the bug, how to reproduce
> said bug (if known), and why/when it was fixed and/or closed.
While I understand your desire to have the info concentrated in one place,
I'm not real keen on creating yet another special file to maintain and
distribute.
o The changelog contains (or should contain) the list of bugs
closed by a given release (as opposed to bugs that are closed
without changes to the package, such as pilot error).
o All the other info should be in the BTS.
I can imagine (but am not volunteering to implement!) a fairly simple
tool that searches a change file for "closes=#xxxxx" (or whatever the
syntax is), and sucks down the relevant BTS entries. That would seem
to meet the need, and remove a fairly significant burden from the
maintainer.
Steve
Reply to: