Ok, first, with the revamp in development that occurred at Microsoft in the past 6 years, it would take a fool to argue that Microsoft doesn't have a solid development cycle down and a system that creates solid and secure code. Their automated testing and compiler technologies don't need 'kiddies' pulling up www.donkeymonkeypaintball.com just to review stability and security.
Every since the development/security 'reboot' at Microsoft in 2003 the code and quality of coded products coming from Microsoft has exponentially improved to the point that even competitors and fringe OSS projects are looking to Microsoft's development cycles for ideas.
The reason you have nightly builds of OSS is a simple little detail, the author of this article doesn't get. In the OSS world, the users pulling the nightly builds are also a large portion of the developers and are reviewing 'code' and submitting new code to help the OSS project.
There is no reason for MS to provide nightly builds, as the developers ALREADY have nightly/daily buildl access to the products.
Pretty simple if you think about it uh?
|