diff --git a/en/releng/index.sgml b/en/releng/index.sgml index 322fa84885..4dfae3af64 100644 --- a/en/releng/index.sgml +++ b/en/releng/index.sgml @@ -1,295 +1,295 @@ - + %includes; %developers; re@FreeBSD.org'> security-officer@FreeBSD.org'> ]> &header;

This page contains documentation about the FreeBSD release engineering process.

Upcoming Release Schedule

NOTE: Release dates are approximate and may be subject to schedule slippage.

Code-Freeze Status

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. The status of other subtrees such as ports/ and doc/ is also provided below.

Branch Status Contact Notes
HEAD Semi-Frozen &contact.re; Active development branch for -CURRENT. In general, open for commits, although restraint is urged until 5.2-RELEASE is announced. Review by &contact.re; is strongly encouraged for large and/or potentially disruptive commits.
RELENG_5_2 Frozen &contact.re; FreeBSD 5.2 release branch. Post-release code-freeze in preparation for handoff to the security-officer team.
RELENG_5_1 Frozen &contact.so; FreeBSD 5.1 supported security fix branch.
RELENG_5_0 Frozen &contact.so; FreeBSD 5.0 security fix branch (not officially supported).
RELENG_4 Open committers Development branch for 4-STABLE.
RELENG_4_9 Frozen &contact.so FreeBSD 4.9 supported security fix branch.
RELENG_4_8 Frozen &contact.so; FreeBSD 4.8 supported security fix branch.
RELENG_4_7 Frozen &contact.so; FreeBSD 4.7 security fix branch (not officially supported).
RELENG_4_6 Frozen &contact.so; FreeBSD 4.6 security fix branch (not officially supported).
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).
Subtree Status Contact Notes
ports/ Open freebsd-ports FreeBSD Ports Collection.
doc/ Open freebsd-doc SGML/XML based documentation set.
www/ Open freebsd-doc FreeBSD Web site sources.

Release Engineering Documentation

Release Engineering Team

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;, &a.steve;, &a.rwatson;, &a.jhb;, &a.bmah;, 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.murray;, &a.jhb;, &a.rwatson;, &a.scottl;

ia64 Platform REs (re-ia64@FreeBSD.org) : &a.marcel;, &a.peter;

i386 Platform REs (re-x86@FreeBSD.org) : &a.murray;, &a.jhb;, &a.rwatson;, &a.bmah;, &a.scottl;

pc98 Platform REs (re-pc98@FreeBSD.org) : &a.nyan;

sparc64 Platform REs (re-sparc64@FreeBSD.org) : &a.jake;, &a.tmm;, &a.rwatson;, &a.jhb;, &a.murray;, &a.phk;, &a.scottl;

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;, &a.lioux;, &a.marcus;

Frequently Asked Questions

Where can I find the release directory or ISO images for older FreeBSD releases?

The FreeBSD Project does not maintain a centralized historical archive of old release ISO images, but there are still many options. First, try looking on http://www.freebsdmirrors.org. If you are unable to find an FTP mirror that still contains the release you are looking for, then you can email CDROM vendors to see if they have any old releases available. In September 2003, we know of a case where FreeBSD 1.1 was used in a court of law to invalidate a bogus software patent. Clearly, older releases can be very important in some situations.

&footer;