OpenBSD Software Development Process

• Fixed deadlines discourage massive changes

  • Frequent snapshots (weekly near release)
    • System always in a ready-to-build state
    • No extended period when system "closed for repairs"
  • Release every 6 months (always on time or early)
    • Features dropped if not release-worthy
    • Tree locked before release (fixes only)
    • Intensive testing by developers and users
    • New features only introduced after unlock

• Features vs. deadline debate

  • Features get left out
    • i386 APM delayed by one release
    • Some architectures left out if unstable