I totally agree with ProThoughts and I'm pretty sure "We all need to contribute in some way to make Q2A better" really summarizes the whole issue. Many users ask and very few users give. And despite the fact that few users are capable of writing code (and even less of them actually do so) I'm considerably surprised that very few users give their time for other additional tasks that can really improve new releases.
I agree with Gurjyot on the fact that more developing hands would, of course, decrease release time. However, waiting for a "development team" to come in order to help with testing is not only utopic but also not exactly accurate. The reason is that this behaviour makes the assumption that currently there is nothing to test, which is not the case. Every merge in the dev (and now in the 1.8) branch could/should (must?) be tested. I've created an issue (bug #488), which in QA jargon would be a showstopper, and so far nobody noticed it (because no one was actually testing that).
In fact, a matter of weeks ago, ProThoughts created this post in here http://www.question2answer.org/qa/55467 which was very helpful as nobody had noticed that issue before and it was critical. Now it is fixed. So it is proven that testing indeed helps.
So I want to emphasize that I like the idea of people actually spending time on making things better and getting their hands dirty (because there is no other way). However, it is also important to understand that anyone can contribute (developers, testers, designers, etc) as anyone can create pull request in GitHub, or create an issue detailing steps to reproduce an unexpected behaviour (bug) or even post a question here asking for assistance on how to do so.
