[arch-general] [arch-dev-public] Allow comments on closed bugs?

Allan McRae allan at archlinux.org
Sat Mar 13 00:38:16 CET 2010


On 13/03/10 09:13, Xavier Chantry wrote:
> On Fri, Mar 12, 2010 at 11:39 PM, Allan McRae<allan at archlinux.org>  wrote:
>> On 13/03/10 08:35, Aaron Griffin wrote:
>>>
>>> Does anyone have an opinion on this?
>>>
>>> In my eyes, I imagine the kind of people who want this feature simply
>>> wish to argue about the closing. I've had to deal with enough PM
>>> requests in the past to know that this _does_ happen.
>>>
>>> Opinions?
>>>
>>
>> I really do not see the need.
>>
>> If a bug is wrongly closed ->  request a reopen.
>> If you just want to confirm a bug has been fixed, there is no need... we
>> already closed the bug report.
>> If there is a "better" fix, reopen request or new bug report.
>>
>
> Closing bugs should not be a race, I had several times the feeling
> that a bug was closed too fast and it can indeed be annoying.
> Ideally the one who opened the bug should give an ACK for having their
> bug closed.
> There is always something to say. At least a confirmation that the bug
> was fixed. Eventually a comment about how it was fixed.
> And you might have additional information / explanation /
> clarification that is mostly interesting for the people who followed
> that bug.
> It seems completely stupid to need a reopen request just to do that.

If we need a confirmation the bug is fixed, then the bug should not be 
closed straight away.  But if a bug is definitely fixed and I close it, 
I really do not need further confirmation it is fixed.  I fact, the only 
time I ever want to hear about the bug again is if it is not fixed.

Given the useless reopen requests I have seen and denied repeatedly 
(such as patching in a new feature), I really would not like to 
continually be notified of such posts.  So closing a bug becomes 1) 
remove yourself from assignees, 2) remove from notification, 3) close bug.

Allan


More information about the arch-general mailing list