Hi, On Thu, Jun 16, 2022 at 05:10:41AM +0000, André Flechs wrote: > > For the others: Please only add them when you are sure they are resolved. > > If you are not sure or you do not have the time for them, please leave > > them untouched. > > How should I write the changelog to close unreproducible or fixed bugs?
You don't. Closing a bug via the changelog is only for bugs which are resolved by this changelog entry. Ideally you have verified this yourself rather than relying on (educated) guess work. For the "fixed" one that is true with your upload I suppose? If not, but in an earlier version you would write a mail to <bugnr>-done@b.d.o with a Version pseudo-header and some free-form text saying something like "This bug was fixed in version 42-1 with the change <quote changelog> hence I am closing as done. Feel free to reopen if this remained unresolved for you". The unreproducible ones you could close the same way without a Version header and some friendly free-form text saying something like "Closing as it is unreproducible (for years) and no more information could be acquired. Feel free to reopen if this still happens for you with more information so we can hopefully find and fix the issue". How friendly (or not) you want to be is your choice of course, both are just condensed examples of what I tend to do. Have a look at the developer-reference which has the entire chapter 5.8 dedicated to "Handling bugs" explaining how to deal with these and many other 'buggy situations' (SCNR). It also explains and points to further documentation about our BTS so that you will know what I mean above with pseudo-headers and -done without me repeating it here. Best regards David Kalnischkies
signature.asc
Description: PGP signature
