diff --git a/en/releases/6.0R/schedule.sgml b/en/releases/6.0R/schedule.sgml
index 11d134c8fa..15f995695e 100644
--- a/en/releases/6.0R/schedule.sgml
+++ b/en/releases/6.0R/schedule.sgml
@@ -1,181 +1,181 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
 <!ENTITY base CDATA "../..">
 <!ENTITY email 'freebsd-qa'>
-<!ENTITY date "$FreeBSD: www/en/releases/6.0R/schedule.sgml,v 1.3 2005/06/11 18:25:55 murray Exp $">
+<!ENTITY date "$FreeBSD: www/en/releases/6.0R/schedule.sgml,v 1.4 2005/06/11 23:42:57 murray Exp $">
 <!ENTITY local.rel "6.0">
 <!ENTITY local.rel.tag "6_0">
 <!ENTITY title "FreeBSD &local.rel; Release Process">
 <!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
 ]>
 
 <html>
 &header;
 
 <h1>Introduction</h1>
 
 <p>This is a specific schedule for the release of FreeBSD &local.rel;.  For
   more general information about the release engineering process,
   please see the <a href="&base;/releng/index.html">Release
   Engineering</a> section of the web site.</p>
 
 <p>General discussions about the release engineering process or
   quality assurance issues should be sent to the public <a
   href="mailto:FreeBSD-qa@FreeBSD.org">freebsd-qa</a> mailing list.
   <a
   href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a>
   requests should be sent to <a
   href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>.</p>
 
 <h1>Schedule</h1>
 
 <table class="tasklist" border="3" cellpadding="5" cellspacing="0">
   <tr class="heading">
     <th>Action</th>
     <th>Expected</th>
     <th>Actual</th>
     <th>Description</th>
   </tr>
 
   <tr>
     <td>Reminder announcement</td>
     <td>3&nbsp;June&nbsp;2005</td>
     <td>3&nbsp;June&nbsp;2005</td>
     <td>Release Engineers send announcement email to
       developers with a rough schedule for the FreeBSD
       &local.rel; release.</td>
   </tr>
 
   <tr>
     <td>Announce the Ports Freeze</td>
     <td>TBD</td>
     <td>--</td>
     <td>Someone from <tt>portmgr@</tt> should email
     <tt>freebsd-ports@</tt> to set a date
     for the week long ports freeze and tagging of the ports tree.</td>
   </tr>
 
   <tr>
     <td>Code freeze begins</td>
     <td>10&nbsp;June&nbsp;2005</td>
     <td>10&nbsp;June&nbsp;2005</td>
     <td>After this date, all commits to HEAD must be approved by <a
       href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>.  Certain highly
       active documentation committers are exempt from this rule for
       routine man page / release note updates.  Heads-up emails
       should be sent to the developers, as well as <tt>stable@</tt>
       and <tt>qa@</tt> lists.</td>
   </tr>
 
 <!-- doceng should tweak these values after we commit it to CVS -->
   <tr>
     <td>Announce <tt>doc/</tt> tree slush</td>
     <td>TBD</td>
     <td>--</td>
     <td>Notification of the impending <tt>doc/</tt> tree slush should
       be sent to <tt>doc@</tt>.</td>
   </tr>
 
 <!-- portmgr should tweak these values after we commit it to CVS -->
   <tr>
     <td>Ports tree frozen</td>
     <td>TBD</td>
     <td>--</td>
     <td>Only approved commits will be permitted to the <tt>ports/</tt>
       tree during the freeze.</td>
   </tr>
 
 <!-- doceng should tweak these values after we commit it to CVS -->
   <tr>
     <td><tt>doc/</tt> tree slush</td>
     <td>TBD</td>
     <td>--</td>
     <td>Non-essential commits to the <tt>en_US.ISO8859-1/</tt> subtree
       should be delayed from this point until after the <tt>doc/</tt>
       tree tagging, to give translation teams time to synchronize
       their work.</td>
   </tr>
 
 <!-- doceng should tweak these values after we commit it to CVS -->
   <tr>
     <td><tt>doc/</tt> tree tagged.</td>
     <td>TBD</td>
     <td>--</td>
     <td>Version number bumps for <tt>doc/</tt> subtree.
       <tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>doc/</tt>.  <tt>doc/</tt>
       slush ends at this time.</td>
   </tr>
 
   <tr>
     <td><tt>RELENG_6</tt> branch</td>
     <td>10&nbsp;July&nbsp;2005</td>
-    <td>--</td>
+    <td>11&nbsp;July&nbsp;2005</td>
     <td>The new major version branch is created. Update <tt>newvers.sh</tt>
       and <tt>release.ent</tt> on various branches involved.</td>
   </tr>
 
   <tr>
     <td><tt>RELENG_6_0</tt> branch</td>
     <td>1&nbsp;Aug&nbsp;2005</td>
     <td>--</td>
     <td>The new release branch is created. Update <tt>newvers.sh</tt>
       and <tt>release.ent</tt> on various branches involved.</td>
   </tr>
 
 <!-- portmgr should tweak these values after we commit it to CVS -->
 <!-- packages should be loaded on ftp-master at least two days before -->
 <!-- release bits get loaded to avoid network congestion problems -->
   <tr>
     <td>Ports tree tagged</td>
     <td>TBD</td>
     <td>--</td>
     <td><tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>ports/</tt>.</td>
   </tr>
 
   <tr>
     <td>Ports tree unfrozen</td>
     <td>TBD</td>
     <td>--</td>
     <td>After the <tt>ports/</tt> tree is tagged,
       the <tt>ports/</tt> tree will be re-opened for commits, but
       commits made after tagging will not go in &local.rel;-RELEASE.</td>
   </tr>
 
   <tr>
     <td>Final package build starts</td>
     <td>TBD</td>
     <td>--</td>
     <td>The ports cluster and
       <a href="http://pointyhat.FreeBSD.org">pointyhat</a>
       build final packages.</td>
   </tr>
 
   <tr>
     <td>Announcement</td>
     <td>15&nbsp;Aug&nbsp;2005</td>
     <td>--</td>
     <td>Announcement sent out after a majority of the mirrors have
       received the bits.</td>
   </tr>
 
   <tr>
     <td>Turn over to the secteam</td>
     <td>TBD</td>
     <td>--</td>
     <td>RELENG_&local.rel.tag; branch is handed over to
       the FreeBSD Security Officer Team in one or two weeks after the
       announcement.</td>
   </tr>
 </table>
 
 <h1>Additional Information</h1>
 
 <ul>
   <li><a href="todo.html">FreeBSD &local.rel; developer todo list.</a></li>
   <li><a href="approvals.html">FreeBSD &local.rel; Code Freeze Commit Approval List.</a></li>
   <li><a href="&base;/releng/index.html">FreeBSD Release Engineering website.</a></li>
 </ul>
 
     &footer;
 
   </body>
 </html>

Action	Expected	Actual	Description
Reminder announcement	3 June 2005	3 June 2005	Release Engineers send announcement email to developers with a rough schedule for the FreeBSD &local.rel; release.
Announce the Ports Freeze	TBD	--	Someone from `portmgr@` should email `freebsd-ports@` to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins	10 June 2005	10 June 2005	After this date, all commits to HEAD must be approved by re@FreeBSD.org. Certain highly active documentation committers are exempt from this rule for routine man page / release note updates. Heads-up emails should be sent to the developers, as well as `stable@` and `qa@` lists.
Announce `doc/` tree slush	TBD	--	Notification of the impending `doc/` tree slush should be sent to `doc@`.
Ports tree frozen	TBD	--	Only approved commits will be permitted to the `ports/` tree during the freeze.
`doc/` tree slush	TBD	--	Non-essential commits to the `en_US.ISO8859-1/` subtree should be delayed from this point until after the `doc/` tree tagging, to give translation teams time to synchronize their work.
`doc/` tree tagged.	TBD	--	Version number bumps for `doc/` subtree. `RELEASE_&local.rel.tag;_0` tag for `doc/`. `doc/` slush ends at this time.
`RELENG_6` branch	10 July 2005	--	11 July 2005	The new major version branch is created. Update `newvers.sh` and `release.ent` on various branches involved.
`RELENG_6_0` branch	1 Aug 2005	--	The new release branch is created. Update `newvers.sh` and `release.ent` on various branches involved.
Ports tree tagged	TBD	--	`RELEASE_&local.rel.tag;_0` tag for `ports/`.
Ports tree unfrozen	TBD	--	After the `ports/` tree is tagged, the `ports/` tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts	TBD	--	The ports cluster and pointyhat build final packages.
Announcement	15 Aug 2005	--	Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam	TBD	--	RELENG_&local.rel.tag; branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.