7 - The same applies to new features. The software is modular - so ideally new features should be released as new modules - not updates to the core. If the new features cannot be released in this manner then you need to go rethink the way that the module system works. The other benefit that releasing features as modules has, is that if one is broken, the issue is perceived as being with the module - not the core software. All a simple case of perception. The first priority should be to get the core see more working correctly first, and then essential modules followed by new features. I would put a hold on features until the bugs are addressed first - regardless of the noise from the forums.

8 - Draft up some procedures for how releases are handled, packaged and released - including what to do if there is an issue. Also look at procedures and methods for development and testing - including a better beta test program, and how bug reporting is handled. Once you have decided on these methods - stick to them. What you are doing here is creating a company procedures manual - or at least the start of one - everyone gets a copy and everyone follows it - everyone knows what they should be doing and everyone pulls in the right direction. You can also expand on this to include lots of other stuff - like how mods operate in the forums, how you answer the phone - whatever it is that needs to go in there. This is an essential part of ISO9001, start getting this together now and you can eventually go for accreditation.