We now are down to the Release Candidate stage of the R1/beta4 release process! There were some important fixes to the kernel, bootloader, and drivers since TC0, so if you can, please do test these builds also.
The builds, sha256sums, and signatures can be downloaded from RC0 LINK REMOVED , Alex (or from your IPFS console, if you have one of those.)
If there are any critical regressions you notice compared to TC0, please report them immediately. Otherwise, within a few days we will likely release the full R1/beta4.
Yes, if you are using R1/beta4 TC0 you should just be able to update as-normal.
Do note there were some fixes to the EFI loader, though, so if you have that installed on your system EFI partition you will have to update it manually.
Is there an easy to find change log of what did change between those two releases? Will grab the RC now and give it a whirl on the same machines I did before.
I suppose you mean the changes between the first r1beta4 test image and this latest RC. You wonât be able to directly compare them - maybe if you roughly know the date of their respective releases - here you find the commit log of the beta4 branch (you can switch at the top right): https://cgit.haiku-os.org/haiku/log/?h=r1beta4
If the UEFI volume were to be served as a separate document in a future release, could it be maintained by a dummy target in HaikuPorts or the main Haiku Repo? It might save some bandwidth to not have to download a whole ISO DVD image just for the UEFI volume contents. I realize that in a beta release, these things will not happen overnight. Would a zipfile or other archive format be adequate to store the files in until it can be unpacked into place? (Iâm thinking about the way that the default version of Java is installed as a dummy package on HaikuPorts so that it can be maintained in conjunction with other version control techniques.)
Will you present the release notes for comment before we roll out the release?
Just to lower the odds important things are missed. For example, Iâd expect to have the issue of Web+ locking curl thread mentioned in the âKnown Issuesâ. It seriously spoils the browsing fun and will get noticed.
I just noticed a Radeon HD accelerant in the proper folder and my card seems to already be using it! @3dEyes , do you have the source for Warzone 2100 handy? I want to take it for a spin! I tried building from the unmodified sources but the texture compressor started looking for a BSD looking header thatâs not there called sys/timex.h.
Update:
I got the texture compressor to compile but now the RE2 regular expression library doesnât seem to work right. I tried the accelerant under Bugdom and it works great!
Tested this on a M1 MacBook Pro using UTM using default settings.
Booting:
Installation media boots no problem. After installation, wonât boot from hard drive using EFI (I tried both GUID and Intel partition map). It will boot from the hard drive with legacyBIOS by unchecking EFI Boot in QEMU settings under tweaks.
Mouse:
Once booted into either the hard drive or the installation media the mouse is unresponsive for about 30secs to a minute and then it works no problem. If you select Force PS/2 controller from the QEMU settings the mouse works without issue.
Shutdown and Rebooting:
Selecting Shutdown the system will shutdown without issue using both EFI(installation media) and legacyBIOS(installation media and hard drive) options. Using legacyBIOS it will deadlock on âAsking other processes to quitâ when trying to restart, using EFI it can reboot without issue. IMO this problem might be on the UTM side because Iâve had other virtual machines deadlock on restart using legacyBIOS.
Later today I"ll upgrade my Pentium 4 with beta 3 to this version and Iâll let you know if there are any issues that might pop up on that computer.
I intend to do a major overhaul of those release notes before they get published on the main website, to be sure, but Iâll try to leave in the important bits others have noted.
There is now an RC1, which patches RC0 in some pretty minor ways (fixing the Welcome and Quick Tour page loads, mostly.) You can download it from RC1 LINK REMOVED , Alex. Thanks again for testing!
I would wait until after the new year to release Beta 4.
Releasing during a holiday will not be good for publicity. Most people will be on vacation with their families and will not have time for testing a new release. News sites will not have time to publish news, and few will read them.
The opposite is usually true after a holiday: people are tired of being on holiday (bored) and looking for something to do. So a release date a few days into the new year would be the best option.
Hmm, perhaps thatâs true for commercial projects, but I was thinking just the opposite. When I had a âregularâ job, I would have more time for Haiku and other such things during the holidays, and then after the New Year and back to the office, Iâd have less again.
Maybe some people will not check out Haiku until after the new year even if we release tomorrow (as currently planned), but is that really a problem? I donât think weâre trying to catch some kind of âcritical momentâ here. If the Promotion Team were more active this seems to be the kind of thing they could evaluate and make a formal decision on, but otherwise I donât see a reason to delay the release arbitrarily hoping for âmore publicityâ due to some kind of magically better timing.
, 
Alex (or from your IPFS console, if you have one of those.)
