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.
The previous report involved a lot of travelling around and attending various events and conferences. This month is quite different as some of us are locked home due to the ongoing pandemic. We already know some of the next planned events such as the JDLL and FLISOL are cancelled (for good reasons).
Anyway, the activity on Haiku has not slowed down, so let's see what's happening there. This report covers hrev53875-hrev53995.
It's time for the monthly report for January (and half of February as well). This report convers hrev53715-hrev53874 and some real world activities.
Unit Tests It's about time the unit tests for Haiku get some serious attention and fixes. Kyle Ambroff-Kao is currently working on them and fixing various issues.
This month he fixed problems in the app and support kits tests, identifying deviations fro, BeOS, some on purpose, some that could be regressions.
This 2019/2020 Google Code-in (GCI) was the 10th iteration in as many years and according to Google's stats it was the most successful yet: In 7 weeks 3,566 students from 76 countries finished 20,840 tasks for 29 open source organizations!
Haiku was one of those organizations - the only open source project, by the way, that participated in all 10 editions of GCI - and we had our share of dedicated students that completed numerous tasks, big and small.
I have not used this blog in a while, except for the monthly activity report. But it's time for a clarification.
Lately, several people (some newcomers, some long time members of the community) have started contacting me by private messages (either by e-mail or IRC chat). Sometimes it was the right thing to do, there are parts of the code for which I'm indeed the best person to ask, and sometimes things are not to be discussed on public channels (for example, because it involves personal data that should stay private).
Hello and welcome to the (almost) monthly activity report for December 2019! December wasn't the busiest for Haiku code-wise, but nonetheless we saw a lot of Google Code-In contributions. This year marks the 10th anniversary of GCI, in which Haiku has participated since the very beginning.
On the non-coding side, GCI participants wrote new virtualization guides: alwayslivid wrote a guide on AWS and rewrote the old Xen one, trungnt2910 wrote a guide on qemu, R4H33M wrote a guide on Vultr and redsPL's (hey, that's me!
The last two months have been quite busy for me and I had no time to write up a report. Remember that everyone is welcome to contribute to the website and if you wand to write the report from time to time, this would be much appreciated, by me because I wouldn't need to do it, and by others because they will enjoy reading things written with a different style and perspective.
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.