This report covers revisions hrev54947-hrev54978 (that was a quiet month in Haiku)
HaikuDepot Andrew Lindesay continues his work on cleaning HaikuDepot sources and removing a custom-made List class to use standard (BeAPI and C++ stl) containers. There were some regressions in the process, that were found and identified.
He also fixed various other bugs.
non-x86 ports tqh is working on the 64bit ARM port, doing the package bootstrap, fixing the compiler configuration, and adding missing pieces of platform specific code.
Hello everyone, apparently we made it to 2021! This year we will see the 20th anniversary of Haiku.
This report covers hrev54806-hrev54947.
Architectures, ports, bootloaders PulkoMandy fixed the build of the openfirmware bootloader for PowerPC. It had been broken by changes for SPARC support. The openfirmware code to set up the splash screen was also fixed to work on sparc.
tqh continues his work on cleaning and simplifying our EFI support.
Welcome to the November-December activity report!
This report covers hrev54716-hrev54805 (about 5 weeks of work).
Code cleanup mt fixed various warnings, use-after-free, memory leaks, and dead code problems detected by the clang static analyzer.
X512 reworked app_server memory management to use owning pointers and avoid some memory leaks and use-after-free cases. This led to a rework of the classes used for that purpose, in particular AutoDeleter and its variants, to be more efficient and more flexible.
Welcome to the October activity report!
I had managed to get other people to write the report for a few months, but not for October, apparently. So, I’m back!
This report covers hrev54609-hrev54715 (about a month and a half work).
The focus is not much on new and exciting features this month, there is a lot of bug fixing and cleanup work going on, as well as some performance improvements, and compatibility fixes for easier application porting.
Welcome to the May-June 2020 activity report!
Are we released yet? Yes! You probably already know, the Beta 2 version has shipped and is available for download. There was a lot of work done towards the release, and then some of us decided to take a break from Haiku for a few weeks to compensate for it.
Google Summer of Code The Google Summer of Code is already reaching it’s mid-point with the end of the first month of coding period.
Welcome to the April 2020 activity report!
Are we released yet? The big news first: a timeline has been set for Beta 2! If all goes well, it will be released by the end of May. Of course, this means everyone has been scrambling for last minute changes this month instead of stabilizing everything. We are now in “soft freeze”, and the branch will be created on Friday.
Now is a good time to test nightly builds on all your machines, help with the translations, and make that bugreport you’ve been postponing for months.
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.
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).
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.