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."
This sounds a lot like Debian's release process. Debian's primary release delays in the past have been infrastructure issues rather than software stability issues -- things like getting the right set of architectures on their mirrors, or getting security infrastructure set up for the new release.
I may very well be that the thing that makes this work is not only the release management practices, but also whatever they do to avoid security problems in the first place.
I couldn't finishing watching the video...(sorry guys...I bet there was some great info in there tho)...I'm not as developie. Anyways...Check the freaking art on their site! Developer Dudes...You change your marketing style just a bit...You'll get people asking for your disk...and then they might even install and try out your OS. Make the two forms of art work together. Developing + Painting...merge the right combination...then...\m/()\m/
Seconded.
In English we don't put a space.
But if dargaud is French, for example, that's the way he and every single one of his countrymen have always written question marks.
No, your children are not the special ones. Nor are your pets.