What's New in Haiku development
The Haiku source is continually built and released for testing purposes nearly every day. You can download and install these latest snapshots to check out the latest features and bug-fixes.
Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.
If you're OK with this, you can find further instructions at our Nightly image page.
Another year, another Google Code-In! The Haiku project is proud to announce that it will be participating in the 2019 Google Code-In!
Together with 28 other open source projects, we’ll mentor students between 13 and 17 years of age through a variety of large and small tasks. The aim is to introduce them to the work and community of open source projects, while benefitting ourselves from their work and energy, and maybe even by gaining future contributors.
Hi there, it’s time for the monthly report!
This report covers hrev53461-hrev53529. Let’s see what happened this month in Haiku.
Non-x86 support Some initial work for ARM64 was completed by kallisti5. This includes setting up the Haikuports package declarations, writing the early boot files, and in general getting the buildsystem going. Jaroslaw Pelczar also contributed several further patches (some of these still undergoing review), providing the initial interrupt handling support, and various stubs to let things compile
TLDR: pkgman install nodejs
Hi there, it's time for the monthly report again! This report covers hrev53338-hrev53461. It's been a busy month!
User interface Andrew Lindesay continue his work on HaikuDepot, tweaking the BarberPole look, adding a display of "usage conditions" (EULA, license, etc) from packages, Ryan Leavengood also worked in this area, making sure if you open an existing hpkg file with HaikuDepot, it will offer you to uninstall the package if it's currently installed.
Introduction Hey there beautiful person reading this post. We are in the endgame now (Ha get it avengers reference!). Yes, Google summer of code 2019 is coming to an end. Phew couldn’t say how 3 months passed by, but this is one of my most memorable experiences I will never forget. So let me wrap GSOC with this final report. Buckle up tight it’s going to be a long post…
Welcome to the monthly report for July 2019! Most of the more interesting changes this month have been from myself in the way of performance optimizations, so I’m writing the progress report this month so I can talk about those in some detail.
This report covers hrev53238-hrev53337 (158 commits.)
Optimizations! Now that Haiku has entered the beta phase, and after the work over the past year or so spent fixing the majority of known kernel crashes and other general instabilities, it is high time we start paying more attention to the whole system’s performance.
PVS studio has just published a series of 3 articles looking over errors and bugs they identified in our sourcecode. PVS is a code static analysis tool that identifies code likely to be incorrect.
They had already run a similar scan back in 2015. At the time, their tools ran on Windows only which had made this quite a challenge for them. They are now more Linux friendly, so it was much easier for them to perform the scan.