Haiku R1/Beta1 Ships After Nearly Six Years of Work Since Alpha 4
The first beta release of Haiku R1 arrived on September 28, 2018 — a milestone that had been anticipated for years, marking the project's transition from alpha-quality software toward an eventual stable 1.0.
On September 28, 2018, the Haiku project released R1/Beta1, its first beta-designated release — arriving nearly six years after Alpha 4, the last release in an alpha series that began with R1/Alpha 1 back in September 2009, and marking a significant milestone in the project’s long path toward a stable 1.0 release.
Why the gap between alpha and beta was so long
Haiku’s alpha releases were explicitly early, rough snapshots; the long stretch between Alpha 4 and Beta1 reflected the scale of engineering work required to bring the operating system’s package management system, driver support, and core application suite to a level the project considered genuinely beta-quality — including the package management system built on packagefs that fundamentally changed how software was installed and managed on Haiku.
What Beta1 actually delivered
The release included substantially improved hardware compatibility, a more complete WebPositive browser, and the maturing package management infrastructure that replaced Haiku’s earlier, more ad hoc software installation approach — collectively representing the difference between “an OS you experiment with in a VM” and “an OS approaching genuine daily-driver viability” for an increasing (if still small) group of users.
Why “beta” was a meaningful, deliberate label change
Moving from “alpha” to “beta” numbering wasn’t cosmetic — it signaled the Haiku project’s own assessment that the remaining work before a 1.0 release was refinement and stabilization of existing functionality, rather than building out fundamentally missing subsystems, a distinction that mattered for a all-volunteer open-source project managing expectations about its own maturity honestly.
The releases that followed
Subsequent beta releases — R1/Beta 2, Beta 3, R1/Beta 4, and R1/Beta 5 — continued this same steady, incremental refinement path, each shipping roughly one to two years apart as the project worked methodically toward an eventual stable 1.0.
Sources: