I was adding a bug to Perl::Tidy, and noticed another bug in the same queue that was no longer a bug (i.e. had been fixed), yet it wasn't marked as such (https://rt.cpan.org/Ticket/Display.html?id=31741).
I wanted to mark it closed, but got permission denied -- so tried to 'claim' the bug (set owner) so I could mark it 'fixed'-- that didn't work either. I did set a 'fixed in' version, but doesn't seem that useful. Would it be that much of a pain if a registered user of rt.cpan.org was able to perform 'administrative' actions such as closing out bugs that are 'fixed', given that the owner of that queue doesn't seem to have closed out any of the bugs in the queue for over 3 years? I'm NOT asking to take over the module -- I just happened to notice a bug 'related' to the one that I filed (regarding the new features added in 5.10) -- i.e. the bug that no longer is present regarded the '//=' operator, while I was adding a new bug about 2 places in the code that needed 2 or 3 of the new keywords (when/given/default). Since I'd just been in the code and saw most of the support for the new keywords and syntax, the //= bug stood out to me as something that I thought would have been addressed (since I've used that construct in my code). Tried it to make sure -- seems to work 'fine' (no error message from perltidy) and seems to be formatted as expected. Since the original bug said an error was emitted by perltidy, and most certainly that is not the case, it no longer valid. Since I just added a bug, thought I'd do the favor of closing one! :-) However, alas, no go. Comments? Shouldn't be able to? Not something that should be added? Or sufficient safeguards with registration to allow such 'help' (considering owner isn't bothering to close it even though I'm pretty sure it was fixed back in the 2009 version). Linda
