Category Archives: FreeBSD 8.0

FreeBSD RELENG_8 created

Yesterday Ken Smith created the RLENG_8, which is required before being able to release any 8.x version at all. This is the first step that will finally lead up to BETA3, after which RC1 is planned. Beta3 also marks the end of the “liberal” ‘ok we still allow some new features if they had previously been discussed’. No more new features will be inserted when BETA3 becomes live. I will try to make a nice list of what’s new for 8.0 the moment BETA3 is tagged. The release is one step closer again!

FreeBSD 8.0-BETA1

Dear FreeBSD users!

Some of you may have not yet noticed, but FreeBSD 8.0 release cycle has begun its latest stage, i.e. the first public beta release, FreeBSD 8.0-BETA1, has been released today. The final release is due about the end of this summer, so stay tuned.

The ISO images should be by now available on most of the FreeBSD mirror sites, and you are the most welcome to test those. We would like to hear your feedback, so that any outstanding bugs can be resolved before 8.0-RELEASE is out.

Please read the announcement carefully, as it contains some important information, mainly that this release still contains a lot of debugging features enabled by default (and as such is not ready for production environment). By now, the freebsd-update tool should be also ready for use.

This page may be of interest to you as well, as it contains some publicly accessible (but not an official standpoint of our release engineering team) information about the progress, known issues and open tasks involved in the release of FreeBSD 8.0.

On the other hand, an article by Ivan Voras talks about features that will, or might be present in the final release of FreeBSD 8.0, so if you are wondering about what’s cooking for this release, you definitely want to check that page out.

FreeBSD 8.0 Slush

The FreeBSD 8.0 code slush had been announced. This means that large projects are no longer allowed to do “drive by commits” to the head branch, but that there is an organisation behind it that checks everything and makes sure there are enough people to cover the project and make sure it’s in the best possible shape before the release. The release will take a little to get going, but the process had been started. From here on the team will have to manouver through a pipe that keeps getting smaller and smaller. If your favorite new feature is not in yet, don’t hold your breath because this might mean that it will take a little longer to get it in a first -RELEASE installation. Stay tuned!