The views issue queue is officially Huge. It might even be *(&)ing huge at this point, but I'm not sure where the cutoff between huge and *(&)ing huge actually is. Either way, it's way, way, way beyond my control. It's like a giant yard that, no matter how much you trim, the grass always grows faster than you can grow it.
It's not like I totally ignore the queue, but to be fair, it takes a lot of time to go through some of this stuff. I just went through some 50 issues and really I've barely dented the thing.
A lot of the stuff in the support queue isn't too bad. Lots of it is easy because the poster didn't give enough info, and it can be changed to active (needs more info) which I automatically filter out of my lists.
I could really use some help doing some weeding on that queue! I know most people can't do much for the bug/feature queue, but the support queue is often a lot more straightforward. Lots of people asking how to do relatively common tasks.

QA team as possible solution
I'd like to see a "QA team" as a possible solution.
Potential tasks include helping create (and execute) test plans for Drupal core or populare contrib modules, helping wrangle the queues of popular modules, helping close/clarify stale issues. Etc.
Lots of folks already do this - let's get organized, build that base up bigger, and do it really well.
See my proposed QA Team for Drupal session in Barcelona for more information.
Post new comment