This report covers hrev58487 through hrev58583.
omesh-barhate contributed a patch to add a context menu to WebPositive’s bookmark bar items, to allow them to be edited more easily. humdinger cleaned up the strings in the new context menu and enhanced its functionality, and removed the “move to front” logic in the Downloads window.
Thank you all involved for your work an for keeping all us informed!
Does this mean also the code that signals and catches ESOCKTNOSUPPORT?
Another busy month! Nice to see a bunch of new contributors - Welcome! - keep them patches coming… 
Kudos to all involved from here too! A big thanks to the new contributors also!
The new error isn’t used anywhere yet, no. But some of the other ESOCK... aren’t either anyway.
It’s nice to see so many new contributors this month.
Welcome to all the new developers 
Nice to see Haiku in press/media like Phoronix and Reddit.
Thank you for all of your work.
Many new contributors! Awesome!
Hmmm…wonder why there are suddenly new contributors? Could it have been the discussion on “How to get to R1”. Because it eliminated some perceived blockages and lowered the barrier to progress? And, so, anything more along those lines could bring in even more contributors.
For example, displaying a list of sections of Haiku that are R1 ready - and those not. Something like this
Again, it makes it look like things are happening, and R1 is getting closer.
Some of them are likely considering GSoC participation, and having an early start. They have been asking questions on IRC and on the forum.
You can use Trac to look at the list of issues by components. I think you will notice that all of the components have at least 1 ticket in the R1 milestone. So, nothing is ready 
Kernel: Custom Query – Haiku
Tracker: Custom Query – Haiku
PoorMan: Custom Query – Haiku
MultiMedia: Custom Query – Haiku
TV: Custom Query – Haiku (no tickets found, apparently it is ready)
But really, this is not how the work is organized, there are no separate teams for any of these, and often there are issues that end up impacting multiple components. That’s why we stopped having separate reports for each of them many years ago.
Instead you have a global progress bar for R1: Roadmap – Haiku
It currently has 555 tickets left to go. If we try to look at the state near the start of each year:
Looking before that, you see a lot more tickets, but sometime in 2021 we had a run through the tickets and moved a lot of things to a new R1.1 milestone.
So, the number of tickets to get to R1 was more or less constant, until Waddlesplash started working full time for Haiku, and now it is decreasing. But there are still several years of work to do at the current rate.
What an amazing month. Thank you everyone.
I have published the quarterly report for linuxfr. You can read it (in French) here:
It sums up the last 3 activity reports (november to january) and I try to give a bit of a higher level view of things when I can.
(I used to do yearly reports, but the one for 2024 was rejected because it was too long, and later split into multiple parts. So now it’s quarterly reports).
Considering that beta 6 got less tickets than beta 1-5, does that mean the time for beta 6 to be ready will be slightly shorter than that of the previous milestones?
The ticket counter for milestones goes up all the time because every time a bug is fixed, it gets recorded as having been fixed for the next milestone, which right now is beta6 of course.
As for the next release, we’ll see what happens. There’s no sense in putting out a release if there’s not really many differences from the previous one. But already since beta5 there has been a lot of work done on the kernel, at least…