Hi Matthew Macdonald-Wallace wrote: > fixes before rolling them out company wide, however frequently when I > produce a fix, I'm told that I'm not allowed to deploy it because it > hasn't been tested.
Hacking at Windows that way massively increases the complexity of support. If you find such a bug in Ubuntu you can file it on launchpad, maybe track it down yourself and submit a patch, and stay in touch with the whole thing, then deploy a new package when it's fixed (building your own if necessary in the interim). Next time you dist-upgrade the machine it will install a new version of the package and all will continue as expected. Going back to the Windows world, your registry fix is going to persist indefinitely, even if it gets subsequently fixed by a Hotfix or a Service Pack. That may have unexpected, unwanted or worse, undefined consequences. Even if you do track down the problem, you can't feed it back upstream as easily, so why does it matter that you save time and money by quickly re-imaging the PC? You forgot: 0) Make use of your support contract for Windows. You do have a support contract, right? ;) > 1) Leave the problem as it is and live with it Windows depends on being a known target, not a highly moving target, so I would always advise against deviating from the expected footprint any more than is necessary. Cheers, -- Chris Jones [EMAIL PROTECTED] www.canonical.com -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.kubuntu.org/UKTeam/
