This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients Arfrever, eric.araujo, mbussonn, ned.deily, r.david.murray, ronaldoussoren, willingc
Date 2016-07-22.13:57:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469195875.22.0.788880978617.issue8406@psf.upfronthosting.co.za>
In-reply-to
Content
I'm sorry if my comment was too harsh, it wasn't intended as such. I was surprised at seeing a number of e-mails about issues that were closed because they were out of date.

I don't agree with closing old issues when there is actionable content in them because that might result in losing valuable information as closed issues are effectively gone. 

Closing old issues is fine when it is clear that the are no longer relevant, but that should IMHO be done with a message that explains why the issue is closed (such as when an issue can no longer be reproduced in supported branches on Python and/or on supported OS releases).

BTW. Feel free to ping me about issues assigned to me when they appear to be no longer relevant but you're not sure.
History
Date User Action Args
2016-07-22 13:57:55ronaldoussorensetrecipients: + ronaldoussoren, ned.deily, eric.araujo, Arfrever, r.david.murray, willingc, mbussonn
2016-07-22 13:57:55ronaldoussorensetmessageid: <1469195875.22.0.788880978617.issue8406@psf.upfronthosting.co.za>
2016-07-22 13:57:55ronaldoussorenlinkissue8406 messages
2016-07-22 13:57:54ronaldoussorencreate