On Wed, Feb 19, 2020 at 10:10:27AM +0100, Thomas Goirand wrote: > Thanks, but I don't need you to micro-manage the bugs in the BTS for me.
I'm not really micro-managing anything for you. I'm just making sure that the information in the BTS is correct. Not necessarily for you, but for anybody working on QA issues (which may be anybody, not just you). > FYI, the package has been uploaded to security-master, and will soon > reach the security repositories, which is why I didn't care much about > this bug being closed (and I prefer it to be closed, so it isn't "on my > way" when reviewing the team's bug list). Glad to know a fixed version has been uploaded to security, but I'm sure there must be already some BTS tag for that (for example, "pending" or "fixed"), which will help you to put bugs "outside your way" without incorrectly closing them. There is a reason why we use the changelog as the preferred method to close bugs: We do it to ensure that the bug is only closed when a fixed version is actually available in the archive, so that bugs are not closed in error. This is valid for unstable, but also for stable and for security. So, if you did a security upload and wrote a Closes statement in the changelog, then the thing you should not care much is really about it being open. Thanks.
