Quality Assurance

In light of recent public criticisms about Trinity's stability, do we have a plan or do we allow for sufficient time for usability testing? The focus seems to be about patching, packaging, and releases. Perhaps with the next release we should introduce a fixed time for serious usability testing? Proverbially, we all eat our own dog food before releasing the software? If a wider window for testing means a shorter window for code hacking then I vote for that. We don't adopt a testing window and code freeze as long as a large project like Debian, :) but we should officially promote a wide enough window to eat our own dog food. :) We touched upon this topic yesterday but I want to bring the topic to the table in a more "official" manner. :) Darrell