It depends on your development methodology really. You might often have just cosmetic issues that end up never getting fixed because they are low on the priority list. What I would like to see is some kind of customer approvals group which has some representation of the customer base, which has the final say whats going into each release.
Maybe rather than it being dictated to us what is going into each release, a list of features with estimates could be voted on every month or so by the community. Personally I believe giving the customers some kind of power is the best option to keep a happy user base. Just at the moment I don't know how items are decided to be added to releases, whether a mixture of bug fixes and enhancements is chosen periodically. Maybe one of the Dev's can shed some light on this....
I would rather give them the trust that they know what needs to and what can wait to be fixed then have the "'customer base"" vote an such things and because they are working hard on such votes some security issue pops up and cause 1 let alone any more bans to happen...