When to close bugs - possible solution
- To: Debian Developers <debian-devel@lists.debian.org>
- Subject: When to close bugs - possible solution
- From: Torsten Landschoff <t.landschoff@gmx.net>
- Date: Wed, 1 Sep 1999 14:08:25 +0200
- Message-id: <[🔎] 19990901140825.B1116@wormhole.galaxy>
- In-reply-to: <19990831170225.C4430@justice.loyola.edu>; from Michael Stone on Tue, Aug 31, 1999 at 05:02:25PM -0400
- References: <87906t3swt.fsf@pfaffben.user.msu.edu> <19990830204031.AB4941957@hobbes.home.ruud.org> <19990830213942.A26847@ecn.purdue.edu> <19990831141342.A16020@pimlott.ne.mediaone.net> <19990831170225.C4430@justice.loyola.edu>
On Tue, Aug 31, 1999 at 05:02:25PM -0400, Michael Stone wrote:
> Then the proper solution is to make the BTS preserve closed bug reports,
> not to force maintainers to track releases.
We can do this in dinstall alone - just let dinstall set the severity to fixed
and retitle the bug to "fixed in $version: $subject". Then after a release a
script has to run over the BTS closing all the bugs with a subject like this
(taking into account the version which is in the release).
Comments? Coders? ;)
cu
Torsten
Attachment:
pgp31bpYTk1UD.pgp
Description: PGP signature
Reply to: