FreeBSD 9.2 Is Behind Schedule, RC4 Released
The release of FreeBSD 9.2 was supposed to happen by the end of August, but instead we're now up to the fourth release candidate.
Like Fedora releases, FreeBSD releases have also become notorious for rarely shipping on time per their release engineering schedule. FreeBSD 9.2 was originally hoped for release on 31 August after the schedule was announced on 23 June, but now as of this week we're up to a 9.2-RC4 version. The FreeBSD developers hope RC4 is the final test release before doing the "RELEASE" build, which could come in the next week or two, if all goes well at this stage.
FreeBSD 9.2-RC4 changes around the boot loader logo, fixes a file-system bug, fixes to some programs for segmentation faults and deadlocks, and a couple other random changes.
For those wishing to learn more about FreeBSD 9.2-RC4, read the mailing list release announcement.
There aren't too many exciting user-facing changes for FreeBSD 9.2, but on the horizon for FreeBSD 10 are many great features including AMD Radeon KMS support, GCC is no longer part of the base system, and the Bhyve virtualization hypervisor.
Like Fedora releases, FreeBSD releases have also become notorious for rarely shipping on time per their release engineering schedule. FreeBSD 9.2 was originally hoped for release on 31 August after the schedule was announced on 23 June, but now as of this week we're up to a 9.2-RC4 version. The FreeBSD developers hope RC4 is the final test release before doing the "RELEASE" build, which could come in the next week or two, if all goes well at this stage.
FreeBSD 9.2-RC4 changes around the boot loader logo, fixes a file-system bug, fixes to some programs for segmentation faults and deadlocks, and a couple other random changes.
For those wishing to learn more about FreeBSD 9.2-RC4, read the mailing list release announcement.
There aren't too many exciting user-facing changes for FreeBSD 9.2, but on the horizon for FreeBSD 10 are many great features including AMD Radeon KMS support, GCC is no longer part of the base system, and the Bhyve virtualization hypervisor.
3 Comments