Rahul Sundaram wrote:
I didnt claim that all updates need to be pushed to the testing repository however if there are exceptions then the rationale behind those exceptions should be better communicated and in case of general guidelines, better documented. Security fixes for might directly go into updates repository while major revisions of packages should go through updates-testing repository is a simple enough policy to enforce for example. I dont for a moment believe that all potential issues or regressions in updates would be caught in the updates-testing repository however there is a potential to have less issues when the testing repository is used by testers who might provide better feedback. The problem is not necessarily what we do but a communication gap in why we do it , the way we do it.
At the very least, it provides a nice comeback when people complain that update X broke feature Y for them.