200 lines
		
	
	
	
		
			6.3 KiB
		
	
	
	
		
			Text
		
	
	
	
	
	
			
		
		
	
	
			200 lines
		
	
	
	
		
			6.3 KiB
		
	
	
	
		
			Text
		
	
	
	
	
	
| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
 | |
| <!ENTITY base CDATA "..">
 | |
| <!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.26 2002/11/19 02:41:41 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><a href="&base;/releases/5.0R/schedule.html">FreeBSD 5.0 Release
 | |
|   Schedule</a>.</li>
 | |
| 
 | |
| <!-- 
 | |
|   <li>General information about committing to -STABLE.</li>
 | |
| -->
 | |
| </ul>
 | |
| 
 | |
| <a name="schedule"></a>
 | |
| <h1>Upcoming Release Schedule</h1>
 | |
| 
 | |
| <ul>
 | |
|   <li><p><strong>December 15, 2002</strong> : <a
 | |
|   href="&base;/releases/5.0R/schedule.html">FreeBSD 5.0</a></p></li>
 | |
|   <li><p><strong>February 1, 2003</strong> : FreeBSD 4.8</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> Frozen </td>
 | |
|     <td> &contact.re; </td>
 | |
|     <td> Active development branch for -CURRENT.  All commits to the
 | |
|       <tt>HEAD</tt> branch must be approved by &contact.re;. </td>
 | |
|   </tr>
 | |
| 
 | |
|   <tr>
 | |
|     <td> <tt>RELENG_4</tt> </td>
 | |
|     <td> Open </td>
 | |
|     <td> &contact.re; </td>
 | |
|     <td> Development branch for 4-STABLE. </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>
 | |
| 
 | |
| </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;
 | |
| 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.</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;</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;</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;</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>
 |