Update dates for the rest of the 5.4 Release schedule (we're now about

two weeks behind).  While here do some sorting based on Expected Date.
This commit is contained in:
Ken Smith 2005-03-24 15:29:01 +00:00
parent 3cdc4f975e
commit 3a23692d99
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=24161

View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.4R/schedule.sgml,v 1.11 2005/03/21 20:18:26 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.4R/schedule.sgml,v 1.12 2005/03/21 23:11:49 hrs Exp $">
<!ENTITY local.rel "5.4">
<!ENTITY local.rel.tag "5_4">
<!ENTITY title "FreeBSD &local.rel; Release Process">
@ -85,68 +85,13 @@
confuses the users who are using the STABLE branch.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>RELENG_&local.rel.tag;</tt> branch</td>
<td>16&nbsp;Mar&nbsp;2005</td>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>14&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>The release branch is created. Update <tt>newvers.sh</tt> and
<tt>release.ent</tt> on various branches involved.</td>
</tr>
<tr>
<td>Unfreeze the tree</td>
<td>16&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>Announcement to developers explaining that
commits to <tt>RELENG_5</tt> no longer require approval. Also
note the policy for commits to the <tt>RELENG_&local.rel.tag;</tt>
branch.</td>
</tr>
<tr>
<td><tt>&local.rel;-RC1</tt></td>
<td>16&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td><tt>newvers.sh</tt> and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>First release candidate</td>
<td>18&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>The first release candidate for the each architecture is
released. ISO images should be uploaded to
<tt>ftp-master.FreeBSD.org</tt>. A network install directory should
be uploaded to <tt>ftp-master.FreeBSD.org</tt>. The
<tt>packages/</tt> directory should be a <em>relative</em> symlink,
as described in the releng article. When the builds begin send a note to
<a href="mailto:mirror-announce@FreeBSD.org">mirror-announce@FreeBSD.org</a>
saying a "Normal Release Cycle" is beginning, RC ISOs and install
directories will be coming through the next few weeks.</td>
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>18&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the first snapshot is uploaded.</td>
</tr>
<tr>
<td>Second release candidate</td>
<td>25&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>Note: the release date of this candidate depends on the user
experience with RC1.</td>
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>25&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the second snapshot is uploaded.</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 -->
@ -158,15 +103,6 @@
tree during the freeze.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>14&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>Notification of the impending <tt>doc/</tt> tree slush should
be sent to <tt>doc@</tt>.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree slush</td>
@ -178,6 +114,41 @@
their work.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree tagged.</td>
<td>28&nbsp;Mar&nbsp;2005</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_&local.rel.tag;</tt> branch</td>
<td>31&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>The release branch is created. Update <tt>newvers.sh</tt> and
<tt>release.ent</tt> on various branches involved.</td>
</tr>
<tr>
<td>Unfreeze the tree</td>
<td>31&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td>Announcement to developers explaining that
commits to <tt>RELENG_5</tt> no longer require approval. Also
note the policy for commits to the <tt>RELENG_&local.rel.tag;</tt>
branch.</td>
</tr>
<tr>
<td><tt>&local.rel;-RC1</tt></td>
<td>31&nbsp;Mar&nbsp;2005</td>
<td>--</td>
<td><tt>newvers.sh</tt> and <tt>release.ent</tt> updated.</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 -->
@ -206,19 +177,48 @@
build final packages.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree tagged.</td>
<td>28&nbsp;Mar&nbsp;2005</td>
<td>First release candidate</td>
<td>2&nbsp;Apr&nbsp;2005</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>
<td>The first release candidate for the each architecture is
released. ISO images should be uploaded to
<tt>ftp-master.FreeBSD.org</tt>. A network install directory should
be uploaded to <tt>ftp-master.FreeBSD.org</tt>. The
<tt>packages/</tt> directory should be a <em>relative</em> symlink,
as described in the releng article. When the builds begin send a note to
<a href="mailto:mirror-announce@FreeBSD.org">mirror-announce@FreeBSD.org</a>
saying a "Normal Release Cycle" is beginning, RC ISOs and install
directories will be coming through the next few weeks.</td>
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>2&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the first snapshot is uploaded.</td>
</tr>
<tr>
<td>Second release candidate</td>
<td>9&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>Note: the release date of this candidate depends on the user
experience with RC1.</td>
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>2&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the second snapshot is uploaded.</td>
</tr>
<tr>
<td>Version numbers bumped.</td>
<td>30&nbsp;Mar&nbsp;2005</td>
<td>14&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>The files listed <a
href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">
@ -228,21 +228,21 @@
<tr>
<td>src tree tagged.</td>
<td>30&nbsp;Mar&nbsp;2005</td>
<td>14&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td><tt>RELENG_&local.rel.tag;_0_RELEASE</tt> tag for <tt>src/</tt>.</td>
</tr>
<tr>
<td>Final builds.</td>
<td>30&nbsp;Mar&nbsp;2005</td>
<td>16&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>Final builds for all architectures in a pristine environment.</td>
</tr>
<tr>
<td>Warn <tt>mirror-announce@FreeBSD.org</tt></td>
<td>30&nbsp;Mar&nbsp;2005</td>
<td>16&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>Heads up email to <a
href="mailto:mirror-announce@FreeBSD.org">mirror-announce@FreeBSD.org</a>
@ -253,7 +253,7 @@
<tr>
<td>Upload to <tt>ftp-master</tt>.</td>
<td>2&nbsp;Apr&nbsp;2005</td>
<td>17&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>Release uploaded to <tt>ftp-master.FreeBSD.org</tt> (packages
should have been done before now, otherwise it chokes the mirror
@ -262,7 +262,7 @@
<tr>
<td>Update man.cgi on the website.</td>
<td>4&nbsp;Apr&nbsp;2005</td>
<td>19&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>Make sure the &local.rel; manual pages are being displayed by default
for the man->web gateway. Also make sure these man pages are
@ -271,7 +271,7 @@
<tr>
<td>Announcement</td>
<td>4&nbsp;Apr&nbsp;2005</td>
<td>19&nbsp;Apr&nbsp;2005</td>
<td>--</td>
<td>Announcement sent out after a majority of the mirrors have
received the bits.</td>
@ -279,7 +279,7 @@
<tr>
<td>Turn over to the secteam</td>
<td>11&nbsp;Apr&nbsp;2005</td>
<td>26&nbsp;Apr&nbsp;2005</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