FreeBSD Release Engineering

Murray Stokely


Legal Notice
Last modified on 2017-03-31 22:36:27Z by gjb.


This document is outdated and does not accurately describe the current release procedures of the FreeBSD Release Engineering team. It is retained for historical purposes. The current procedures used by the FreeBSD Release Engineering team are available in the FreeBSD Release Engineering article.

This paper describes the approach used by the FreeBSD release engineering team to make production quality releases of the FreeBSD Operating System. It details the methodology used for the official FreeBSD releases and describes the tools available for those interested in producing customized FreeBSD releases for corporate rollouts or commercial productization.

[ Split HTML / Single HTML ]

Table of Contents
1. Introduction
2. Release Process
3. Release Building
4. Distribution
5. Extensibility
6. Lessons Learned from FreeBSD 4.4
7. Future Directions
8. Acknowledgements

1. Introduction

The development of FreeBSD is a very open process. FreeBSD is comprised of contributions from thousands of people around the world. The FreeBSD Project provides Subversion [1] access to the general public so that others can have access to log messages, diffs (patches) between development branches, and other productivity enhancements that formal source code management provides. This has been a huge help in attracting more talented developers to FreeBSD. However, I think everyone would agree that chaos would soon manifest if write access to the main repository was opened up to everyone on the Internet. Therefore only a select group of nearly 300 people are given write access to the Subversion repository. These committers [2] are usually the people who do the bulk of FreeBSD development. An elected Core Team [3] of developers provide some level of direction over the project.

The rapid pace of FreeBSD development makes the main development branch unsuitable for the everyday use by the general public. In particular, stabilizing efforts are required for polishing the development system into a production quality release. To solve this conflict, development continues on several parallel tracks. The main development branch is the HEAD or trunk of our Subversion tree, known as FreeBSD-CURRENT or -CURRENT for short.

A set of more stable branches are maintained, known as FreeBSD-STABLE or -STABLE for short. All branches live in a master Subversion repository maintained by the FreeBSD Project. FreeBSD-CURRENT is the bleeding-edge of FreeBSD development where all new changes first enter the system. FreeBSD-STABLE is the development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT and have been thoroughly tested by our user community.

The term stable in the name of the branch refers to the presumed Application Binary Interface stability, which is promised by the project. This means that a user application compiled on an older version of the system from the same branch works on a newer system from the same branch. The ABI stability has improved greatly from the compared to previous releases. In most cases, binaries from the older STABLE systems run unmodified on newer systems, including HEAD, assuming that the system management interfaces are not used.

In the interim period between releases, weekly snapshots are built automatically by the FreeBSD Project build machines and made available for download from The widespread availability of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with Subversion and make buildworld [4] helps to keep FreeBSD-STABLE in a very reliable condition even before the quality assurance activities ramp up pending a major release.

In addition to installation ISO snapshots, weekly virtual machine images are also provided for use with VirtualBox, qemu, or other popular emulation software. The virtual machine images can be downloaded from

The virtual machine images are approximately 150MB xz(1) compressed, and contain a 10GB sparse filesystem when attached to a virtual machine.

Bug reports and feature requests are continuously submitted by users throughout the release cycle. Problems reports are entered into our Bugzilla database through the web interface provided at

To service our most conservative users, individual release branches were introduced with FreeBSD 4.3. These release branches are created shortly before a final release is made. After the release goes out, only the most critical security fixes and additions are merged onto the release branch. In addition to source updates via Subversion, binary patchkits are available to keep systems on the releng/X.Y branches updated.

1.1. What this article describes

The following sections of this article describe:

Section 2, “Release Process”

The different phases of the release engineering process leading up to the actual system build.

Section 3, “Release Building”

The actual build process.

Section 5, “Extensibility”

How the base release may be extended by third parties.

Section 6, “Lessons Learned from FreeBSD 4.4”

Some of the lessons learned through the release of FreeBSD 4.4.

Section 7, “Future Directions”

Future directions of development.

All FreeBSD documents are available for download at

Questions that are not answered by the documentation may be sent to <>.
Send questions about this document to <>.