diff --git a/en/releases/7.2R/schedule.sgml b/en/releases/7.2R/schedule.sgml
index c1511d8904..d282593dab 100644
--- a/en/releases/7.2R/schedule.sgml
+++ b/en/releases/7.2R/schedule.sgml
@@ -1,201 +1,201 @@
 <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
 <!ENTITY base CDATA "../..">
 <!ENTITY email 'freebsd-qa'>
-<!ENTITY date "$FreeBSD: www/en/releases/7.2R/schedule.sgml,v 1.6 2009/04/03 17:15:05 blackend Exp $">
+<!ENTITY date "$FreeBSD: www/en/releases/7.2R/schedule.sgml,v 1.7 2009/04/10 12:52:02 blackend Exp $">
 <!ENTITY local.rel "7.2">
 <!ENTITY local.rel.tag "7_2">
 <!ENTITY title "FreeBSD &local.rel; Release Process">
 <!ENTITY % navinclude.download "INCLUDE">
 ]>
 
 <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 pending release and known issues should be
     sent to the public
     <a href="mailto:FreeBSD-stable@FreeBSD.org">freebsd-stable</a> mailing list.
     <a href="&base;/doc/en_US.ISO8859-1/books/handbook/freebsd-glossary.html#MFC-GLOSSARY">MFC</a>
     requests should be sent to
     <a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>.</p>
 
   <h1>Schedule</h1>
 
   <table class="tblbasic">
     <tr class="heading">
       <td>Action</td>
       <td>Expected</td>
       <td>Actual</td>
       <td>Description</td>
     </tr>
 
     <tr>
       <td>Reminder announcement</td>
       <td>16&nbsp;March&nbsp;2009</td>
       <td>17&nbsp;March&nbsp;2009</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>3&nbsp;April&nbsp;2009</td>
       <td>3&nbsp;April&nbsp;2009</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>23&nbsp;March&nbsp;2009</td>
       <td>23&nbsp;March&nbsp;2009</td>
       <td>After this date, all commits to RELENG_7 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>--</td>
       <td>3&nbsp;April&nbsp;2009</td>
       <td>Notification of the impending <tt>doc/</tt> tree slush should
 	be sent to <tt>doc@</tt>.</td>
     </tr>
 
     <tr>
       <td>Ports tree frozen</td>
       <td>13&nbsp;April&nbsp;2009</td>
-      <td>--</td>
+      <td>13&nbsp;April&nbsp;2009</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>10&nbsp;April&nbsp;2009</td>
       <td>10&nbsp;April&nbsp;2009</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>17&nbsp;April&nbsp;2009</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>BETA1</tt> builds</td>
       <td>30&nbsp;March&nbsp;2009</td>
       <td>31&nbsp;March&nbsp;2009</td>
       <td>Begin BETA1 builds.</td>
     </tr>
 
     <tr>
       <td><tt>RELENG_7_2</tt> branch</td>
       <td>10 April 2009</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>
 
     <tr>
       <td><tt>RC1</tt> builds</td>
       <td>13&nbsp;April&nbsp;2009</td>
       <td>--</td>
       <td>Begin RC1 builds.</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>20&nbsp;April&nbsp;2009</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>20&nbsp;April&nbsp;2009</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>20&nbsp;April&nbsp;2009</td>
       <td>--</td>
       <td>The ports cluster and
 	<a href="http://pointyhat.FreeBSD.org">pointyhat</a>
 	build final packages.</td>
     </tr>
 
     <tr>
       <td><tt>RC2</tt> builds</td>
       <td>20&nbsp;April&nbsp;2009</td>
       <td>--</td>
       <td>Begin RC2 builds.</td>
     </tr>
 
     <tr>
       <td><tt>RELEASE</tt> builds</td>
       <td>1&nbsp;May&nbsp;2009</td>
       <td>--</td>
       <td>Begin RELEASE builds.</td>
     </tr>
 
     <tr>
       <td>Announcement</td>
       <td>4&nbsp;May&nbsp;2009</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	16 March 2009	17 March 2009	Release Engineers send announcement email to developers with a rough schedule for the FreeBSD &local.rel; release.
Announce the Ports Freeze	3 April 2009	3 April 2009	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	23 March 2009	23 March 2009	After this date, all commits to RELENG_7 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	--	3 April 2009	Notification of the impending `doc/` tree slush should be sent to `doc@`.
Ports tree frozen	13 April 2009	--	13 April 2009	Only approved commits will be permitted to the `ports/` tree during the freeze.
`doc/` tree slush	10 April 2009	10 April 2009	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.	17 April 2009	--	Version number bumps for `doc/` subtree. `RELEASE_&local.rel.tag;_0` tag for `doc/`. `doc/` slush ends at this time.
`BETA1` builds	30 March 2009	31 March 2009	Begin BETA1 builds.
`RELENG_7_2` branch	10 April 2009	--	The new release branch is created. Update `newvers.sh` and `release.ent` on various branches involved.
`RC1` builds	13 April 2009	--	Begin RC1 builds.
Ports tree tagged	20 April 2009	--	`RELEASE_&local.rel.tag;_0` tag for `ports/`.
Ports tree unfrozen	20 April 2009	--	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	20 April 2009	--	The ports cluster and pointyhat build final packages.
`RC2` builds	20 April 2009	--	Begin RC2 builds.
`RELEASE` builds	1 May 2009	--	Begin RELEASE builds.
Announcement	4 May 2009	--	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.