227 lines
7.4 KiB
Text
227 lines
7.4 KiB
Text
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
|
<!ENTITY base CDATA "..">
|
|
<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.38 2003/02/25 16:43:59 bmah Exp $">
|
|
<!ENTITY email 're'>
|
|
<!ENTITY title "Release Engineering Information">
|
|
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
|
|
<!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
|
|
<!ENTITY contact.re '<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>'>
|
|
<!ENTITY contact.so '<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>'>
|
|
]>
|
|
|
|
<html>
|
|
&header;
|
|
|
|
<p>This page contains documentation about the FreeBSD release
|
|
engineering process.</p>
|
|
|
|
<ul>
|
|
<li><a href="#schedule">Upcoming Release Schedule</a>.</li>
|
|
<li><a href="#freeze">Code Freeze Status</a>.</li>
|
|
<li><a href="&base;/releng/charter.html">Charter for the Release
|
|
Engineering Team</a>.</li>
|
|
<li><a href="#docs">Release Engineering Documentation</a>.</li>
|
|
<li><a href="#team">Current Release Engineering Team</a>.</li>
|
|
|
|
<!--
|
|
<li>General information about committing to -STABLE.</li>
|
|
-->
|
|
</ul>
|
|
|
|
<a name="schedule"></a>
|
|
<h1>Upcoming Release Schedule</h1>
|
|
|
|
<ul>
|
|
<li><p><strong>March 24, 2003</strong> : <a href="&base;/releases/4.8R/schedule.html">FreeBSD 4.8</a></p></li>
|
|
</ul>
|
|
|
|
<a name="freeze"></a>
|
|
<h1>Code-Freeze Status</h1>
|
|
|
|
<p>The following table lists the code freeze status for the major
|
|
branches of the <tt>src/</tt> subtree of the FreeBSD CVS
|
|
repository. Commits to any branch listed as "frozen" must first be
|
|
reviewed and approved by the relevant contact party.</p>
|
|
|
|
<p>Note that the <tt>ports/</tt>, <tt>doc/</tt>, and <tt>www/</tt>
|
|
subtrees are not branched and not covered by this table.</p>
|
|
|
|
<table border="3" cellpadding="2" cellspacing="0">
|
|
<tr>
|
|
<th> Branch </th>
|
|
<th> Status </th>
|
|
<th> Contact </th>
|
|
<th> Notes </th>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>HEAD</tt> </td>
|
|
<td> Semi-Frozen </td>
|
|
<td> &contact.re; </td>
|
|
<td> Active development branch for -CURRENT. Commits to this
|
|
branch will be in 5.1-RELEASE and 5-STABLE. Sometime around
|
|
the release of 5.1-RELEASE or 5.2-RELEASE, we will branch RELENG_5 (for 5-STABLE) and this
|
|
branch will then be known at 6-CURRENT. With that in mind,
|
|
developers should treat this as a "STABLE" branch for the next few
|
|
months and focus on fixing bugs to make 5-STABLE a success.
|
|
Invasive commits to <tt>HEAD</tt> must be coordinated and approved
|
|
by &contact.re;.</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_5_0</tt> </td>
|
|
<td> Frozen </td>
|
|
<td> &contact.so; </td>
|
|
<td> FreeBSD 5.0 supported security fix branch. </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_4</tt> </td>
|
|
<td> Frozen </td>
|
|
<td> &contact.re; </td>
|
|
<td> Development branch for 4-STABLE. Currently in code-freeze in preparation
|
|
for FreeBSD 4.8. </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_4_7</tt> </td>
|
|
<td> Frozen </td>
|
|
<td> &contact.so; </td>
|
|
<td> FreeBSD 4.7 supported security fix branch. </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_4_6</tt> </td>
|
|
<td> Frozen </td>
|
|
<td> &contact.so; </td>
|
|
<td> FreeBSD 4.6 supported security fix branch. </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_4_5</tt> </td>
|
|
<td> Frozen </td>
|
|
<td> &contact.so; </td>
|
|
<td> FreeBSD 4.5 security fix branch (not officially supported). </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_4_4</tt> </td>
|
|
<td> Frozen </td>
|
|
<td> &contact.so; </td>
|
|
<td> FreeBSD 4.4 security fix branch (not officially supported). </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_4_3</tt> </td>
|
|
<td> Frozen </td>
|
|
<td> &contact.so; </td>
|
|
<td> FreeBSD 4.3 security fix branch (not officially supported). </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_3</tt> </td>
|
|
<td> Open </td>
|
|
<td> committers </td>
|
|
<td> Maintenance branch for 3-STABLE (not officially supported). </td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td> <tt>RELENG_2_2</tt> </td>
|
|
<td> Open </td>
|
|
<td> committers </td>
|
|
<td> Maintenance branch for 2.2-STABLE (not officially supported). </td>
|
|
</tr>
|
|
</table>
|
|
|
|
<a name="docs"></a>
|
|
<h1>Release Engineering Documentation</h1>
|
|
|
|
<ul>
|
|
<li><p><a
|
|
href="&base;/doc/en_US.ISO8859-1/articles/releng/index.html">FreeBSD
|
|
Release Engineering</a><br>
|
|
|
|
<small>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.</small></p></li>
|
|
|
|
|
|
<li><p><a
|
|
href="&base;/doc/en_US.ISO8859-1/articles/releng-packages/index.html">FreeBSD
|
|
Release Engineering for Third Party Packages</a><br>
|
|
|
|
<small>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.</small></p></li>
|
|
|
|
<li><p><a
|
|
href="&base;/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">FreeBSD
|
|
5-STABLE Roadmap</a><br>
|
|
|
|
<small>Describes the roadmap for the project for reaching the RELENG_5
|
|
branch. Includes overall status of 5.x, what's left to be done, and
|
|
tentative schedules.</small></p></li>
|
|
|
|
</ul>
|
|
|
|
<a name="team"></a>
|
|
<h1>Release Engineering Team</h1>
|
|
|
|
<p>The primary release engineering team is responsible for approving
|
|
<a
|
|
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a>
|
|
requests during code freezes, setting release schedules, and all of
|
|
the other responsibilities laid out in our <a
|
|
href="&base;/releng/charter.html">charter</a>.</p>
|
|
|
|
<p><strong>Primary RE Team (<a
|
|
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>)</strong> :
|
|
&a.murray;, &a.steve;, &a.rwatson;, &a.jhb;, &a.bmah;, &a.kris;, and
|
|
&a.scottl; form the primary release engineering decision-making
|
|
group.</p>
|
|
|
|
<p>The platform-specific release engineering teams are responsible for
|
|
building and packaging FreeBSD releases on the given platforms.</p>
|
|
|
|
<p><strong>Alpha Platform REs (<a
|
|
href="mailto:re-alpha@FreeBSD.org">re-alpha@FreeBSD.org</a>)</strong> :
|
|
&a.wilko;, &a.obrien;, &a.murray;, &a.jhb;, &a.rwatson;, &a.scottl;, &a.kris;</p>
|
|
|
|
<p><strong>ia64 Platform REs (<a
|
|
href="mailto:re-ia64@FreeBSD.org">re-ia64@FreeBSD.org</a>)</strong> :
|
|
&a.marcel;, &a.peter;</p>
|
|
|
|
<p><strong>i386 Platform REs (<a
|
|
href="mailto:re-x86@FreeBSD.org">re-x86@FreeBSD.org</a>)</strong> :
|
|
&a.murray;, &a.jhb;, &a.rwatson;, &a.bmah;, &a.scottl;, &a.kris;</p>
|
|
|
|
<p><strong>pc98 Platform REs (<a
|
|
href="mailto:re-pc98@FreeBSD.org">re-pc98@FreeBSD.org</a>)</strong> :
|
|
&a.nyan;</p>
|
|
|
|
<p><strong>sparc64 Platform REs (<a
|
|
href="mailto:re-sparc64@FreeBSD.org">re-sparc64@FreeBSD.org</a>)</strong> :
|
|
&a.jake;, &a.tmm;, &a.rwatson;, &a.jhb;, &a.murray;, &a.phk;, &a.scottl;,
|
|
&a.kris;</p>
|
|
|
|
<p>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.</p>
|
|
|
|
<p><strong>Package Builders (<a
|
|
href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>)</strong> :
|
|
&a.asami;, &a.kris;, &a.sobomax;, &a.steve;, &a.will;, &a.knu;</p>
|
|
|
|
&footer;
|
|
</body>
|
|
</html>
|