My take on old issues is this, assuming it&#39;s not my own issue/project (in which case do what you like I guess).<br><br>Bugs:<br>Is it a real bug? If not, active needs more info, by design, or won&#39;t fix.<br>Is it still a bug? Bump it, but do a quick search for duplicate issues<br>
If it&#39;s been fixed 1. try to find a duplicate issue to mark it against if it&#39;s a core bug 2. In contrib, mark to fixed (or sometimes directly to closed if it&#39;s very old), or duplicate, case by case.<br><br>Feature requests:<br>
Is it a valid feature request? No module does this? Not just a support request for configuration?<br>If it fails any of these, won&#39;t fix.<br>If it is valid, bump the version, and generally worth adding a note to explain why it&#39;s still valid.<br>
<br>Tasks and support requests are usually a variation of the above.<br><br>And something has patches attached to it, I usually leave them more open than if not, and generally take a quick look at the patch to see if it&#39;s got any chance of applying. Marking things to needs work keeps the dust monsters a lot happier. And if an issue has been RTBC for more than a couple of months it&#39;s probably at the wrong status.<br>
<br>