Hi all. I just wondered what the procedure is for dealing with very old issues. I've got some in my queue that were last updated 2+ years ago and the projects in question are probably unmaintained now anyway (flexinode, swish-e indexer etc). What do I do? Thanks Adam
Seeing what I saw during these last 3 years, I would say that the powers-above-us will tell you three things: 1. If the issue was created by you, close it 2. If the issue was created by someone else, review it and then close it if you have sure 3. Any other option, don't mess with the issue queue because it will awake the dust monsters ;) Be carefull, Fernando On Mon, Apr 14, 2008 at 10:22 PM, Adam Cooper <adam.j.cooper@gmail.com> wrote:
Hi all.
I just wondered what the procedure is for dealing with very old issues. I've got some in my queue that were last updated 2+ years ago and the projects in question are probably unmaintained now anyway (flexinode, swish-e indexer etc).
What do I do?
Thanks Adam
Fernando Silva wrote:
3. Any other option, don't mess with the issue queue because it will awake the dust monsters ;)
Moving too quickly does see to awaken the "dust monsters". I suggest the T-Rex approach which is move slowly and methodically toward your goal so nobody sees you doing it. ;) Close the worst offenders first and offer the reporter a chance to reopen if still valid in the closing comment. -- Michael Favia michael@favias.org tel. 512.585.5650 http://michael.favias.org
My take on old issues is this, assuming it's not my own issue/project (in which case do what you like I guess). Bugs: Is it a real bug? If not, active needs more info, by design, or won't fix. Is it still a bug? Bump it, but do a quick search for duplicate issues If it's been fixed 1. try to find a duplicate issue to mark it against if it's a core bug 2. In contrib, mark to fixed (or sometimes directly to closed if it's very old), or duplicate, case by case. Feature requests: Is it a valid feature request? No module does this? Not just a support request for configuration? If it fails any of these, won't fix. If it is valid, bump the version, and generally worth adding a note to explain why it's still valid. Tasks and support requests are usually a variation of the above. 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'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's probably at the wrong status.
participants (4)
-
Adam Cooper -
catch -
Fernando Silva -
Michael Favia