Salvete! The volunteer model is a good part of what is stalling the process. I can't see that having a single company sign off on their own code will necessarily ameliorate the problem if the companies themselves do not place enough of a value on bug testing that they are willing to include it within their service and enhancement RFPs. I still think of this as a happy problem; we're doing so much it's tough to get to everything. That speaks to planning and prioritisation at the root, though. More eyes are better once again: a single corporation's goals might vary widely with the community's. I am also wary of externalising the bad guy role to the QA or RM. Both of these individuals, regardless of who they are, have always had a heavy burden to carry. I am easier with this concept if it involves bugs that are not critical or blockers, which is what I thought was being proposed initially. I very much agree with Owen and Heather. I feel like there's accord on a year+ being far too long to wait on a new feature of any type. What does everyone feel is the right amount of time before falling back to a more lax protocol? A month has been mentioned, but I wonder if that's not too short. Cheers, Brooke