os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
doc/en/releng/index.sgml
Bruce A. Mah 1a01b15c37 5.3 and 5.4 have been EOL-ed (this actually happened about three weeks 
ago)...change their status here.

Submitted by:	moose at opera dot com
Approved by:	re
2006-11-24 18:06:58 +00:00

425 lines
12 KiB
Text
Raw Blame History

<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.198 2006/11/18 20:26:13 bmah Exp $">
<!ENTITY email 're'>
<!ENTITY title "Release Engineering Information">
<!ENTITY % navinclude.developers "INCLUDE">
<!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>'>
<!ENTITY contact.portmgr '<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>'>
<!ENTITY contact.doc '<a href="mailto:freebsd-doc@FreeBSD.org">freebsd-doc@FreeBSD.org</a>'>
<!ENTITY contact.www '<a href="mailto:freebsd-www@FreeBSD.org">freebsd-www@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><a href="#faq">Frequently Asked Questions</a></li>
<!--
<li>General information about committing to -STABLE.</li>
-->
</ul>
<a name="schedule"></a>
<h2>Upcoming Release Schedule</h2>
<p>NOTE: Release dates are approximate and may be subject to schedule
slippage.</p>
<table class="tblbasic">
<tr>
<th> Date </th>
<th> Event </th>
<th> Information </th>
</tr>
<tr>
<td> September 10, 2006 </td>
<td> Freeze RELENG_6 </td>
<td rowspan="2">
<![ %beta.testing; [
<a href="../where.html#helptest">Pre-release Images</a>,
]]>
<a href="../releases/6.2R/schedule.html">Schedule</a>, <a
href="../releases/6.2R/todo.html">Todo</a>, <a
href="../releases/6.2R/approvals.html">Approvals</a>
</td>
</tr>
<tr>
<td> Mid-December 2006 </td>
<td> Release FreeBSD 6.2 </td>
</tr>
<tr>
<td> TBA </td>
<td> Freeze RELENG_6 </td>
<td> N/A </td>
</tr>
<tr>
<td> TBA </td>
<td> Release FreeBSD 6.3 </td>
<td> N/A </td>
</tr>
<tr>
<td> June, 2007 </td>
<td> Start FreeBSD 7.0 Release Process </td>
<td> N/A </td>
</tr>
</table>
<a name="freeze"></a>
<h2>Code-Freeze Status</h2>
<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. The status of
other subtrees such as <tt>ports/</tt>, <tt>doc/</tt>, and <tt>www/</tt> is also
provided below.</p>
<table class="tblbasic">
<tr>
<th> Branch </th>
<th> Status </th>
<th> Contact </th>
<th> Notes </th>
</tr>
<tr>
<td> <tt>HEAD</tt> </td>
<td> Open </td>
<td> committers </td>
<td> Active development branch for -CURRENT. </td>
</tr>
<tr>
<td> <tt>RELENG_6</tt> </td>
<td> Open </td>
<td> &contact.re; </td>
<td> Development branch for 6-STABLE. Open for commits, but major changes should be coordinated with &contact.re; until 6.2-RELEASE. </td>
</tr>
<tr>
<td> <tt>RELENG_6_2</tt> </td>
<td> Frozen </td>
<td> &contact.re; </td>
<td> FreeBSD 6.2 release branch. </td>
</tr>
<tr>
<td> <tt>RELENG_6_1</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 6.1 supported errata fix branch. </td>
</tr>
<tr>
<td> <tt>RELENG_6_0</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 6.0 supported errata fix branch. </td>
</tr>
<tr>
<td> <tt>RELENG_5</tt> </td>
<td> Open </td>
<td> committers </td>
<td> Development branch for 5-STABLE. </td>
</tr>
<tr>
<td> <tt>RELENG_5_5</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 5.5 supported errata fix branch. </td>
</tr>
<tr>
<td> <tt>RELENG_5_4</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 5.4 errata fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_5_3</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 5.3 errata fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_5_2</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 5.2 / 5.2.1 security fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_5_1</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 5.1 security fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_5_0</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 5.0 security fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_4</tt> </td>
<td> Open </td>
<td> committers </td>
<td> Development branch for 4-STABLE.</td>
</tr>
<tr>
<td> <tt>RELENG_4_11</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 4.11 supported errata fix branch (<a
href="&base;/releases/4.11R/errata_policy.html">errata policy</a>)</td>
</tr>
<tr>
<td> <tt>RELENG_4_10</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 4.10 security fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_4_9</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 4.9 security fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_4_8</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 4.8 security fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_4_7</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 4.7 security fix branch (not officially supported). </td>
</tr>
<tr>
<td> <tt>RELENG_4_6</tt> </td>
<td> Frozen </td>
<td> &contact.so; </td>
<td> FreeBSD 4.6 security fix branch (not officially supported). </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>
<tr class="heading">
<th> Subtree </th>
<th> Status </th>
<th> Contact </th>
<th> Notes </th>
</tr>
<tr>
<td> <tt>ports/</tt> </td>
<td> No sweeping changes until the release of 6.2.
If in doubt, please contact &contact.portmgr;. </td>
<td> &contact.portmgr; </td>
<td> FreeBSD Ports Collection. </td>
</tr>
<tr>
<td> <tt>doc/</tt> </td>
<td> Open </td>
<td> &contact.doc; </td>
<td> SGML/XML based documentation set. </td>
</tr>
<tr>
<td> <tt>www/</tt> </td>
<td> Open </td>
<td> &contact.www; </td>
<td> FreeBSD Web site sources. </td>
</tr>
</table>
<a name="docs"></a>
<h2>Release Engineering Documentation</h2>
<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>Described the roadmap for the project for reaching the RELENG_5
branch. Included overall status of 5.x, what was left to be done, and
tentative schedules. Note that this document is now mainly of
historical interest.</small></p></li>
<li><p><a
href="&base;/doc/en_US.ISO8859-1/articles/version-guide/index.html">Choosing
the FreeBSD Version That Is Right For You</a><br>
<small>How to decide which version of FreeBSD is right for your
needs. Topics include the releases, branches, the difference
between -CURRENT and -STABLE, and the current scheduling goals
of the project.</small></p></li>
</ul>
<a name="team"></a>
<h2>Release Engineering Team</h2>
<p>The primary release engineering team is responsible for approving
<a href="&base;/doc/en_US.ISO8859-1/books/handbook/freebsd-glossary.html#MFC-GLOSSARY">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.re.members; 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.re-alpha;</p>
<p><strong>AMD64 Platform REs (<a
href="mailto:re-amd64@FreeBSD.org">re-amd64@FreeBSD.org</a>)</strong> :
&a.re-amd64;</p>
<p><strong>ia64 Platform REs (<a
href="mailto:re-ia64@FreeBSD.org">re-ia64@FreeBSD.org</a>)</strong> :
&a.re-ia64;</p>
<p><strong>i386 Platform REs (<a
href="mailto:re-x86@FreeBSD.org">re-x86@FreeBSD.org</a>)</strong> :
&a.re-i386;</p>
<p><strong>pc98 Platform REs (<a
href="mailto:re-pc98@FreeBSD.org">re-pc98@FreeBSD.org</a>)</strong> :
&a.re-pc98;</p>
<p><strong>PowerPC Platform REs (<a
href="mailto:re-ppc@FreeBSD.org">re-ppc@FreeBSD.org</a>)</strong> :
&a.re-powerpc;</p>
<p><strong>sparc64 Platform REs (<a
href="mailto:re-sparc64@FreeBSD.org">re-sparc64@FreeBSD.org</a>)</strong> :
&a.re-sparc64;</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 (&contact.portmgr;)</strong> :
&a.portmgr;</p>
<a name="faq"></a>
<h2>Frequently Asked Questions</h2>
<p>Where can I find the release directory or ISO images for older FreeBSD releases?</p>
<p>The FreeBSD Project does not maintain a centralized historical
archive of old release ISO images, but there are still many options.
First, a large collection of the old releases (many complete with the
package sets) is at <a
href="ftp://ftp-archive.FreeBSD.org/pub/FreeBSD-Archive/old-releases/">
ftp://ftp-archive.FreeBSD.org/pub/FreeBSD-Archive/old-releases/</a>.
Second, try looking on <a
href="http://mirrorlist.FreeBSD.org">http://mirrorlist.FreeBSD.org</a>.
If you are unable to find an FTP mirror that still contains the
release you are looking for, then you can email CD-ROM 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.</p>
&footer;
</body>
</html>
Reference in a new issue View git blame Copy permalink