diff --git a/en/releases/6.3R/schedule.sgml b/en/releases/6.3R/schedule.sgml
index 74e9cca6af..3ede477b05 100644
--- a/en/releases/6.3R/schedule.sgml
+++ b/en/releases/6.3R/schedule.sgml
@@ -1,206 +1,206 @@
<!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/6.3R/schedule.sgml,v 1.1 2007/11/25 05:26:46 kensmith Exp $">
+<!ENTITY date "$FreeBSD: www/en/releases/6.3R/schedule.sgml,v 1.2 2007/11/25 18:02:29 blackend Exp $">
<!ENTITY local.rel "6.3">
<!ENTITY local.rel.tag "6_3">
<!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 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="tblbasic">
<tr class="heading">
<td>Action</td>
<td>Expected</td>
<td>Actual</td>
<td>Description</td>
</tr>
<tr>
<td>Reminder announcement</td>
<td>TBD</td>
<td>15 Oct 2007</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>23 Oct 2007</td>
<td>23 Oct 2007</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>18 Nov 2007</td>
<td>18 Nov 2007</td>
<td>After this date, all commits to RELENG_6 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>19 Nov 2007</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>30 Oct 2007</td>
<td>30 Oct 2007</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>25 Nov 2007</td>
<td>25 Nov 2007</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>5 Dec 2007</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>24 Oct 2007</td>
<td>1 Nov 2007</td>
<td>Begin BETA1 builds.</td>
</tr>
<tr>
<td><tt>BETA2</tt> builds</td>
<td>7 Nov 2007</td>
<td>9 Nov 2007</td>
<td>Begin BETA2 builds.</td>
</tr>
<tr>
<td><tt>RELENG_6_3</tt> branch</td>
<td>21 Nov 2007</td>
<td>25 Nov 2007</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>21 Nov 2007</td>
<td>--</td>
<td>Begin RC1 builds.</td>
</tr>
<tr>
<td><tt>RC2</tt> builds</td>
<td>5 Dec 2007</td>
<td>--</td>
<td>Begin RC2 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>7 Nov 2007</td>
+ <td>14 Dec 2007</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>7 Nov 2007</td>
+ <td>14 Dec 2007</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>7 Nov 2007</td>
+ <td>14 Dec 2007</td>
<td>--</td>
<td>The ports cluster and
<a href="http://pointyhat.FreeBSD.org">pointyhat</a>
build final packages.</td>
</tr>
<tr>
<td><tt>RELEASE</tt> builds</td>
<td>19 Dec 2007</td>
<td>--</td>
<td>Begin RELEASE builds.</td>
</tr>
<tr>
<td>Announcement</td>
<td>23 Dec 2007</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="&base;/releng/index.html">FreeBSD Release Engineering website.</a></li>
</ul>
&footer;
</body>
</html>
diff --git a/en/releases/7.0R/schedule.sgml b/en/releases/7.0R/schedule.sgml
index ac1c86aae8..b7de926ffa 100644
--- a/en/releases/7.0R/schedule.sgml
+++ b/en/releases/7.0R/schedule.sgml
@@ -1,230 +1,230 @@
<!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.0R/schedule.sgml,v 1.7 2007/11/25 18:02:29 blackend Exp $">
+<!ENTITY date "$FreeBSD: www/en/releases/7.0R/schedule.sgml,v 1.8 2007/11/30 15:20:03 kensmith Exp $">
<!ENTITY local.rel "7.0">
<!ENTITY local.rel.tag "7_0">
<!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 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="tblbasic">
<tr class="heading">
<td>Action</td>
<td>Expected</td>
<td>Actual</td>
<td>Description</td>
</tr>
<tr>
<td>Reminder announcement</td>
<td>TBD</td>
<td>15 Oct 2007</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>23 Oct 2007</td>
<td>23 Oct 2007</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>18 June 2007</td>
<td>19 June 2007</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>19 Nov 2007</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>30 Oct 2007</td>
<td>30 Oct 2007</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>25 Nov 2007</td>
<td>25 Nov 2007</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>5 Dec 2007</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_7</tt> branch</td>
<td>--</td>
<td>11 Oct 2007</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>BETA1</tt> builds</td>
<td>17 Oct 2007</td>
<td>19 Oct 2007</td>
<td>Begin BETA1 builds.</td>
</tr>
<tr>
<td><tt>BETA2</tt> builds</td>
<td>31 Oct 2007</td>
<td>31 Oct 2007</td>
<td>Begin BETA2 builds.</td>
</tr>
<tr>
<td><tt>BETA3</tt> builds</td>
<td>14 Nov 2007</td>
<td>16 Nov 2007</td>
<td>Begin BETA3 builds.</td>
</tr>
<tr>
<td><tt>BETA4</tt> builds</td>
<td>28 Nov 2007</td>
<td>--</td>
<td>Begin BETA4 builds.</td>
</tr>
<tr>
<td><tt>RELENG_7_0</tt> branch</td>
<td>12 Dec 2007</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>12 Dec 2007</td>
<td>--</td>
<td>Begin RC1 builds.</td>
</tr>
<tr>
<td><tt>RC2</tt> builds</td>
<td>26 Dec 2007</td>
<td>--</td>
<td>Begin RC2 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>7 Nov 2007</td>
+ <td>14 Dec 2007</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>7 Nov 2007</td>
+ <td>14 Dec 2007</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>7 Nov 2007</td>
+ <td>14 Dec 2007</td>
<td>--</td>
<td>The ports cluster and
<a href="http://pointyhat.FreeBSD.org">pointyhat</a>
build final packages.</td>
</tr>
<tr>
<td><tt>RELEASE</tt> builds</td>
<td>9 Jan 2008</td>
<td>--</td>
<td>Begin RELEASE builds.</td>
</tr>
<tr>
<td>Announcement</td>
<td>14 Jan 2008</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>