Re: Handling stale bug reports

On 0808, Paul Wise wrote: >On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote: > >> How should a new maintainer go about closing old bug reports? > >I noticed that you have been: > >Closing bug reports without any explanation. > >Closing what looks like legitimate feature requests. > >Neither of

Re: Handling stale bug reports

On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote: > How should a new maintainer go about closing old bug reports? I noticed that you have been: Closing bug reports without any explanation. Closing what looks like legitimate feature requests. Neither of these is a good idea IMO. -- bye, p

Re: Handling stale bug reports

On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote: > What's the best way to go about handling old bug reports? Triage them; go through each bug, try to find out if it was fixed and which version it was fixed in. For the definitely fixed bugs, close them with a versioned -done message. For the

Handling stale bug reports

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How should a new maintainer go about closing old bug reports? For instance, I recently just took over apt-listchanges and see a lot of old bug reports, including one from the year 2000. I read https://www.debian.org/Bugs/Developer#closing, and it s