Slashdot Mirror
Why OpenBSD's Release Process Works
An anonymous reader writes "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.
Theo de Raadt explains in this presentation how the OpenBSD release process is managed (video) and why it has been such a success."
The majority of people in the world are average, by definition.
Excuse the pedantry, but you're making a big assumption when you're considering that the majority are in the average. For all you know half of people could be extremely bad and the other half extremely bright, leaving no one anywhere near the average.
You just got troll'd!
Way to go Hatta. You just made a fool of yourself.
Now everyone is actually reading you link and realizing what a pathetic Karam troll your post was. Hey, but at least you got a couple of knee jerk GNU fans with mod points to mod you up...
Huff another bong hit and consider this, bro...
If BSD hadn't forked, it would likely be the most predominate x86 *nix, rather than an almost irrelevant footnote in IT history.
As it is, any great concept that the BSD teams developed was eventually incorporated in the more politically unified development culture of Linux. BSD folks tend toward very shallow marketing slogans like "Security, Portability, and whatever" which doesn't cut it when you look at where the actual work is happening. Any meaningful conclusion is that results beat stoner burnout platitudes.
Business. Numbers. Money. People. Computer World.
Watch the video deadshit.
How we know is more important than what we know.