diff --git a/en/releng/index.sgml b/en/releng/index.sgml
index f2b955cfaf..86d82b1e34 100644
--- a/en/releng/index.sgml
+++ b/en/releng/index.sgml
@@ -1,115 +1,121 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
 <!ENTITY base CDATA "..">
-<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.1 2002/03/04 06:49:52 murray Exp $">
+<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.2 2002/03/04 08:19:53 murray Exp $">
 <!ENTITY email 're'>
 <!ENTITY title "Release Engineering Information">
 <!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
 <!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
 ]>
 
 <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>Charter for the Release Engineering Team - <em>Coming Soon</em>.</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/4.6R/schedule.html">FreeBSD 4.6 Release
   Schedule</a>.</li>
-  <li>FreeBSD 5.0 Release Schedule - <em>Coming Soon</em>.</li>
+  <li><a href="&base;/releases/5.0R/schedule.html">FreeBSD 5.0 Release
+  Schedule</a>.</li>
+
 <!-- 
   <li>Information about code freezes.</li>
   <li>General information about committing to -STABLE.</li>
 -->
 </ul>
 
 <a name="schedule"></a>
 <h1>Upcoming Release Schedule</h1>
 
 <ul>
-  <li><p><strong>April 1, 2002</strong> : FreeBSD 5.0 Developer
-Preview 1</p></li>
-  <li><p><strong>June 1, 2002</strong> : <a href="&base;/releases/4.6R/schedule.html">FreeBSD 4.6</a></p></li>
-  <li><p><strong>June 25, 2002</strong> : FreeBSD 5.0 Developer
-Preview 2</p></li>
+  <li><p><strong>April 1, 2002</strong> : <a
+  href="&base;/releases/5.0R/schedule.html">FreeBSD 5.0 Developer
+  Preview 1</a></p></li>
+  <li><p><strong>June 1, 2002</strong> : <a
+  href="&base;/releases/4.6R/schedule.html">FreeBSD 4.6</a></p></li>
+  <li><p><strong>June 25, 2002</strong> : <a
+  href="&base;/releases/5.0R/schedule.html">FreeBSD 5.0 Developer
+  Preview 2</a></p></li>
   <li><p><em>[optionally, a third 5.0 DP if necessary]</em></p></li>
   <li><p><strong>October 1, 2002</strong> : FreeBSD 4.7</p></li>
-  <li><p><strong>November 20, 2002</strong> : FreeBSD 5.0</p></li>
+  <li><p><strong>November 20, 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="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 charter. <em>(coming
   soon)</em>.</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;,
 &a.brian;, 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;, &a.brian;</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.ade;, &a.asami;, &a.kris;, &a.sobomax;, &a.steve;, &a.will;</p>
 
 &footer;
 </body>
 </html>
