[Tracker-discuss] [issue302] make 'closed' issues read-only

[Ronald Oussoren]

Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

David: the nosy list only helps if those on the list actually react to the nosy 
message. I often use the e-mail I get from the tracker as a warning that 
something needs to be done and don't react immediately unless the issue seems 
very critical.

I then use the one of the report on bugs.python.org to check for issues that are 
interesting for me (assigned to me, I'm on the nosy list, ...). Those reports do 
not include issues that are closed, which means that additional messages to an 
already closed issue tend to get ignored.

W.r.t. mudling the news file, I meant Misc/NEWS in Python's distribution. That 
contains longish lists of "Fixes issue #1234: foobar crashes the interpreter", 
where the part after the colon is often the title of the issue. If a new message 
to closed issue #1234 results in a new bugfix you'll get a second "Fixes issue 
#1234" line in a later release of python, which is fine if issue #1234 wasn't 
fixed after all but is confusing if the new message was an unrelated issue.

The reason I wrote this wish is that I have had to ask several users to open a 
new issue because the added a message to an already closed issue, and the new 
message was only slightly related to the issue at hand.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue302>
_______________________________________________________