[llvm-dev] RFC: Bug-closing protocol

Vitaly Buka via llvm-dev llvm-dev at lists.llvm.org
Wed Jun 13 11:52:27 PDT 2018

Sorry, I'll improve messaging.
Most of bugs I closed this way are just "that the bug cannot be reproduced
with trunk" or "not enough information and I don't expect reporter is going
to provide any after so may years".
If I misinterpret the bug, I expect push back from reporter.

On Tue, Jun 12, 2018 at 7:51 AM via llvm-dev <llvm-dev at lists.llvm.org>

> TL;DR: It's okay to close a bug, if you can justify it properly.
> Recently there has been a spate of bug-closing with what I would call
> inadequate documentation.  Comments such as "Obsolete?" or "I assume
> it's fixed" could be applied to nearly every open bug we have.  While
> this does reduce the open bug count--something I have been watching
> with morbid fascination for years--I do fear that the reduction is
> potentially artificial, and incorrectly puts the onus on the original
> bug author to reopen the case.
> I suggest that closing a bug can be done IF AND ONLY IF you also state
> one of the following:
> - that revision NNNNNN actually fixed the bug
> - that the bug cannot be reproduced with revision NNNNNN
> - that the circumstances for the bug don't apply anymore; e.g.,
>   "This is about the makefiles and we don't use makefiles anymore."
> - sound reasons for not fixing something (WONTFIX)
> - some specific and plausible reason to think that a given bug is
>   otherwise inapplicable or obsolete
> In particular, "Obsolete?" and "I assume it's fixed" are NOT enough
> justification to close a bug.
> If people are okay with this, I'd expect adding a new section to the
> Developer Policy is probably the right place to put it.
> Comments/brickbats welcome...
> --paulr
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180613/5d1e8531/attachment-0001.html>

More information about the llvm-dev mailing list