FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux Development

 
 
LinkBack Thread Tools
 
Old 03-12-2010, 09:35 PM
Aaron Griffin
 
Default Allow comments on closed bugs?

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?
 
Old 03-12-2010, 09:37 PM
Daenyth Blank
 
Default Allow comments on closed bugs?

On Fri, Mar 12, 2010 at 17:35, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> Does anyone have an opinion on this?
I can go both ways on it. I think that the *primary* use is just to
whine when a bug is closed, but in the past I've also seen cases where
it legitimately added to the discussion.
 
Old 03-12-2010, 09:39 PM
Allan McRae
 
Default Allow comments on closed bugs?

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.

Allan
 
Old 03-12-2010, 10:13 PM
Xavier Chantry
 
Default Allow comments on closed bugs?

On Fri, Mar 12, 2010 at 11:39 PM, Allan McRae <allan@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.
 
Old 03-12-2010, 10:38 PM
Allan McRae
 
Default Allow comments on closed bugs?

On 13/03/10 09:13, Xavier Chantry wrote:

On Fri, Mar 12, 2010 at 11:39 PM, Allan McRae<allan@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
 
Old 03-12-2010, 10:42 PM
Andrea Scarpino
 
Default Allow comments on closed bugs?

On Friday 12 March 2010 23:39:05 Allan McRae wrote:
> 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.
+1
we do not need comments on closed bug

--
Andrea
 
Old 03-12-2010, 10:48 PM
Aaron Griffin
 
Default Allow comments on closed bugs?

On Fri, Mar 12, 2010 at 5:38 PM, Allan McRae <allan@archlinux.org> wrote:
> So closing a bug becomes 1) remove yourself from
> assignees, 2) remove from notification, 3) close bug.

This is what worries me the most. If comments on old bugs are allowed,
this will become the norm.
 

Thread Tools




All times are GMT. The time now is 01:21 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org