Hello there,
I think it's time for a status update on beta3.
We currently have 3 blocker issues left:
https://dev.haiku-os.org/query?status=assigned&status=in-progress&status=new&status=reopened&milestone=R1/beta3&group=priority&order=priority
#15728 is a crash of app_server while playing youtube videos. Currently it is
not reproductible because youtube video replay does not work at all anymore. I
suggest moving it to a later release for investigation when youtube is fixed
and we can test it again.
#16304 is about various problems encountered by users while testing DriveSetup.
I have made some minor changes (improved UI labels) and also moved several
pre-existing issues into the beta3 milestones, which it would be nice to
investigate. I plan to look into some of them in the next weeks, but help is
always welcome
#16744 is a regression due to the work on packagefs to allow resuming
interrupted downloads. Stippi has been working on this and I think the
remaining part of his changes can be merged soon and should fix the issues
around packagefs for good.
We have one high priority issue: #16746 is about a problem with the text rect
in BTextView when renaming files in Tracker. In some cases the filename ends up
being scrolled off screen. I think it should be moved up to blocker. It is not
that annoying when you know about it, but it's confusing and easy to notice,
and gives a bad impression of Haiku.
Another thing to take care of is #16751. Currently Haiku uses ICU 57, but new
WebKit releases use ICU 66. If we don't update our built-in version of ICU, we
would have to ship the 32bit version with 3 different versions: ICU 57 for
gcc2, ICU 57 for gcc8, and ICU 66 for gcc8. This would result in an increase of
disk usage that I'd rather avoid. This issue also includes an update of the
Noto font, needed for exampel to get the backspace key to be visible in Keymap
preferences.
Is there anything else that should be included in beta3? If not, I think we
should start thinking about a plan for releasing it in the next months. The
original target date was late february (I picked this arbitrarily when creating
the milestone). If that seems a bit too close, I think we can delay it to
sometime in march?
--
Adrien.
