Not quite to a typical engineering process but I'm guessing it's much better than a typical open source project where people just keep hacking the code and do n

Not quite to a typical engineering process but I'm guessing it's much better than a typical open source project where people just keep hacking the code and do not care much the quality (security, performance, code quality, etc). I think the idea is that developers should have some sort of SOP (Standard Operating Procedure). I know some people will moan when they heard that abbreviation, especially if people just want to "hack some code". It comes down to discipline and professionalism really. Interesting video: http://www.youtube.com/watch?v=i7pkyDUX5uM http://www.youtube.com/watch?v=i7pkyDUX5uM "Twelve years ago OpenBSD developers started engineering a release process that has resulted in quality software being delivered on a consistent 6 month schedule -- 25 times in a row, exactly on the date promised, and with no critical bugs. This on-time delivery process is very different from how corporations manage their product releases and much more in tune with how volunteer driven communities are supposed to function. Developer and testing laziness is mostly circumvented and leader frustration is kept to a minimum. The reasons, mechanics and social workings of our process have never been detailed outside the project, but now will be, hopefully providing some insight to others who face delays and quality issues with their own product lines."