[Building Sakai] Why OpenBSD's Release Process Works

Speelmon, Lance Day lance at indiana.edu
Fri Jul 17 07:14:15 PDT 2009


Key points so far:

"All [source tree] locks and unlocks are surprise events"
"Forewarned people are lazy"
"Poor response during the test cycle results in punishment"


Lance Speelmon
Scholarly Technologist

On Jul 17, 2009, at 9:20 AM, Speelmon, Lance Day wrote:

Have not watched yet, but sounds interesting.  L

http://tech.slashdot.org/story/09/07/16/2322203/Why-OpenBSDs-Release-Process-Works?from=rss

"Twelve years ago OpenBSD<http://www.openbsd.org/> 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<http://theos.com/> explains in this presentation how the OpenBSD release process is managed<http://www.youtube.com/watch?v=i7pkyDUX5uM> (video) and why it has been such a success."



Lance Speelmon
Scholarly Technologist

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090717/286f85a1/attachment.html 


More information about the sakai-dev mailing list