I think someone needs to buckle down and go through the bug reports on leaky. It seems like no one is keeping up with the posts, pages of reports still marked New~ I realize that many of the posts there are not actually bugs or issues in Bukkit, and rather issues with server ops using bad plugins or the like, or perhaps using builds between recommended builds. But I've personally added two issues I'd like to see fixed, or at least acknowledged. Ones that I've come across during plugin development, tracing problems I was having back to issues within Bukkit itself. :3 Anyway, I thought I'd give a nudge here, to anyone who cares~ (Oh, and to bump my issues indirectly: http://leaky.bukkit.org/issues/1531 and http://leaky.bukkit.org/issues/1579 )
Are you just behind in the list by a bit? Though it seems only selective posts in the last weeks have any activity. If you are reading every one and not just selected ones at random, it might be good to change the statuses away from New while you are at it, and reject the bad reports like for instance this one: http://leaky.bukkit.org/issues/1466 I'm assuming leaky is being ignored because of all the issues still marked New, with no responses either. :3
It's a public facing issue tracker. We are usually working on more than any one ticket at a time, testing changes and sometimes things don't pan out. Many of the tickets are about possible fixes from Bukkit for a vanilla bug. Sometimes we can do it, sometimes we can't. Changing the status from "New" to anything else is often misleading in these cases. But I, personally, actively go through Leaky a few times every day, whether I mark things as seen or not.
Is there a way to find out if a ticket has been pulled to a private tracker, and its status there? Some sort of feedback would be reassuring, in any case, even if no promises of actual activity are involved. :3 Perhaps setting some sort of status akin to marked read, so the public knows the ticket was read at least.
