This page contains documentation about the FreeBSD release engineering process.
December 15, 2002 : FreeBSD 5.0
February 1, 2003 : FreeBSD 4.8
The following table lists the code freeze status for the major branches of the src/ subtree of the FreeBSD CVS repository. Commits to any branch listed as "frozen" must first be reviewed and approved by the relevant contact party.
Note that the ports/, doc/, and www/ subtrees are not branched and not covered by this table.
| Branch | Status | Contact | Notes |
|---|---|---|---|
| HEAD | Frozen | &contact.re; | Active development branch for -CURRENT. All commits to the HEAD branch must be approved by &contact.re;. |
| RELENG_4 | Open | &contact.re; | Development branch for 4-STABLE. |
| RELENG_4_7 | Frozen | &contact.so; | FreeBSD 4.7 supported security fix branch. |
| RELENG_4_6 | Frozen | &contact.so; | FreeBSD 4.6 supported security fix branch. |
| RELENG_4_5 | Frozen | &contact.so; | FreeBSD 4.5 security fix branch (not officially supported). |
| RELENG_4_4 | Frozen | &contact.so; | FreeBSD 4.4 security fix branch (not officially supported). |
| RELENG_4_3 | Frozen | &contact.so; | FreeBSD 4.3 security fix branch (not officially supported). |
| RELENG_3 | Open | committers | Maintenance branch for 3-STABLE (not officially supported). |
| RELENG_2_2 | Open | committers | Maintenance branch for 2.2-STABLE (not officially supported). |
FreeBSD
Release Engineering
Describes the approach used by the FreeBSD release
engineering team to make production quality releases of the
FreeBSD Operating System. It describes the tools available
for those interested in producing customized FreeBSD releases
for corporate rollouts or commercial
productization.
FreeBSD
Release Engineering for Third Party Packages
Describes the approach used by the FreeBSD release
engineering team to produce a high quality package set
suitable for official FreeBSD release media. This document is
a work in progress, but eventually it will cover the process
used to build a clean package set on the FreeBSD.org "Ports
Cluster", how to configure any other set of machines as a
ports cluster, how to split up the packages for the release
media, and how to verify that a package set is
consistent.
The primary release engineering team is responsible for approving MFC requests during code freezes, setting release schedules, and all of the other responsibilities laid out in our charter.
Primary RE Team (re@FreeBSD.org) : &a.murray; -is the primary RE / chairperson, and &a.steve;, &a.rwatson;, &a.jhb;, -and &a.bmah; form the rest of the primary release -engineering decision-making group.
+href="mailto:re@FreeBSD.org">re@FreeBSD.org) : +&a.murray;, &a.steve;, &a.rwatson;, &a.jhb;, &a.bmah;, &a.kris;, and +&a.scottl; form the primary release engineering decision-making +group.The platform-specific release engineering teams are responsible for building and packaging FreeBSD releases on the given platforms.
Alpha Platform REs (re-alpha@FreeBSD.org) : &a.wilko;, &a.obrien;, &a.murray;, &a.jhb;, &a.rwatson;
i386 Platform REs (re-x86@FreeBSD.org) : &a.murray;, &a.jhb;, &a.rwatson;, &a.bmah;
sparc64 Platform REs (re-sparc64@FreeBSD.org) : &a.jake;, &a.tmm;, &a.rwatson;, &a.jhb;, &a.murray;, &a.phk;
The third party packages in the Ports Collection are managed by the portmgr@ team. Among many other responsibilities, the port managers keep the ports cluster running smoothly to produce binary packages.
Package Builders (portmgr@FreeBSD.org) : &a.asami;, &a.kris;, &a.sobomax;, &a.steve;, &a.will;, &a.knu;
&footer;