Hi Dmitry, Dmitry Smirnov <only...@member.fsf.org> writes: > It's maintainer's job and decision to reopen bugs. Merely re-opening
Ultimately sure but when there's no controversy (i.e. when I assume that both agree that the bug exists) I usually reopen the bug to save time. > bug do not notify maintainers so I wasn't aware that you re-opened > this bug because you didn't bother to explain the reason for > reopening! If any problem is still there you have to share how it is > manifesting. Silent reopening is inappropriate and frustrating. > > Furthermore while you silently re-opened this particular bug (#710886) > in corresponding upstream bug report you admitted that it is not the > problem so now I have to clean up this mess and close our bug with > fears that you might re-open it yet again without even explaining > why... Indeed, I forgot to re-close the bug once I realized that I can't reproduce it in a controlled environment. > Can I trust you to communicate your concerns in the future and refrain > from reopening bugs behind my/everyone's back please? I usually always send unarchive, then reopen and then an explanation of the issue. It was simply a mistake to forget the last step when I realized I need to figure out a new way to simulate the challenging network conditions. I did re-close the upstream bug this time though. -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org