The "by the book" method is to set policies that do not allow developers to receive "silent automatic updates" unless they have been centrally orchestrated by your QA.
Your QA or someone would have a development lab isolated from your real development environment. They would test an update against a number of factors including regression tests that previous stuff works. Then, when satisfied, a Change Request is made, logging what has to be done, specifying how to roll back if it all goes to Ludwig and then a centrally orchestrated update is made to the pre-warned user PCs.
Will you be doing that in future?
Last edited by Suspishio; Aug 17th, 2009 at 8:48 pm. Reason: typo
Reputation Points: 47
Solved Threads: 144
Posting Virtuoso
Offline 1,729 posts
since Aug 2007