diff options
Diffstat (limited to 'en_US.ISO8859-1/htdocs/releases/5.4R/schedule.sgml')
-rw-r--r-- | en_US.ISO8859-1/htdocs/releases/5.4R/schedule.sgml | 333 |
1 files changed, 333 insertions, 0 deletions
diff --git a/en_US.ISO8859-1/htdocs/releases/5.4R/schedule.sgml b/en_US.ISO8859-1/htdocs/releases/5.4R/schedule.sgml new file mode 100644 index 0000000000..26aaa2ec75 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/5.4R/schedule.sgml @@ -0,0 +1,333 @@ +<!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/5.4R/schedule.sgml,v 1.25 2005/10/04 06:52:24 murray Exp $"> +<!ENTITY local.rel "5.4"> +<!ENTITY local.rel.tag "5_4"> +<!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> + <td>Action</td> + <td>Expected</td> + <td>Actual</td> + <td>Description</td> + </tr> + + <tr> + <td>Reminder announcement</td> + <td>31 Jan 2005</td> + <td>31 Jan 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>24 Feb 2005</td> + <td>24 Feb 2005</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><tt>&local.rel;-PRERELEASE</tt></td> + <td>23 Feb 2005</td> + <td>24 Feb 2005</td> + <td><tt>newvers.sh</tt> updated.</td> + </tr> + + <tr> + <td>Code freeze begins</td> + <td>2 Mar 2005</td> + <td>3 Mar 2005</td> + <td>After this date, all commits to the <tt>RELENG_5</tt> branch + 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> + + <tr> + <td><tt><strike>&local.rel;-PRERELEASE</strike></tt><br> + <tt>&local.rel;-BETA1</tt></td> + <td>4 Mar 2005</td> + <td>20 Mar 2005</td> + <td>First public test release build. Note that the release build + name is &local.rel;-BETA1 but <tt>newvers.sh</tt> RELEASE name remains + &local.rel;-PRERELEASE. This is because the name BETA often + confuses the users who are using the STABLE branch.</td> + </tr> + +<!-- doceng should tweak these values after we commit it to CVS --> + <tr> + <td>Announce <tt>doc/</tt> tree slush</td> + <td>14 Mar 2005</td> + <td>25 Mar 2005</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>21 Mar 2005</td> + <td>21 Mar 2005</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><strike>24 Mar 2005</strike><br> + 2 Apr 2005</td> + <td>2 Apr 2005<br> + <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><strike>28 Mar 2005</strike><br> + 11 Apr 2005</td> + <td>12 Apr 2005</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 Mar 2005</td> + <td>3 Apr 2005</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 Mar 2005</td> + <td>3 Apr 2005</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 Mar 2005</td> + <td>3 Apr 2005</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 --> + <tr> + <td>Ports tree tagged</td> + <td>31 Mar 2005</td> + <td>2 Apr 2005</td> + <td><tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>ports/</tt>.</td> + </tr> + + <tr> + <td>Ports tree unfrozen</td> + <td>31 Mar 2005</td> + <td>2 Apr 2005</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>31 Mar 2005</td> + <td>--</td> + <td>The ports cluster and + <a href="http://pointyhat.FreeBSD.org">pointyhat</a> + build final packages.</td> + </tr> + + <tr> + <td>First release candidate</td> + <td>2 Apr 2005</td> + <td>5 Apr 2005</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 Apr 2005</td> + <td>5 Apr 2005</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 Apr 2005</td> + <td>9 Apr 2005</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>9 Apr 2005</td> + <td>11 Apr 2005</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>Third release candidate</td> + <td>16 Apr 2005</td> + <td>16 Apr 2005</td> + <td>Note: the release date of this candidate depends on the user + experience with RC2.</td> + </tr> + + <tr> + <td>Heads up to <tt>-stable</tt></td> + <td>16 Apr 2005</td> + <td>18 Apr 2005</td> + <td>A message should be sent to <tt>qa@FreeBSD.org</tt> and + <tt>stable@FreeBSD.org</tt> after the third snapshot is uploaded.</td> + </tr> + + <tr> + <td>Fourth release candidate</td> + <td>30 Apr 2005</td> + <td>2 May 2005</td> + <td>Note: This is the final release candidate.</td> + </tr> + + <tr> + <td>Heads up to <tt>-stable</tt></td> + <td>1 May 2005</td> + <td>2 May 2005</td> + <td>A message should be sent to <tt>qa@FreeBSD.org</tt> and + <tt>stable@FreeBSD.org</tt> after the fourth snapshot is uploaded.</td> + </tr> + + <tr> + <td>Version numbers bumped.</td> + <td>6 May 2005</td> + <td>6 May 2005</td> + <td>The files listed <a + href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP"> + here</a> are updated to reflect the fact that this is FreeBSD + &local.rel;.</td> + </tr> + + <tr> + <td>src tree tagged.</td> + <td>6 May 2005</td> + <td>6 May 2005</td> + <td><tt>RELENG_&local.rel.tag;_0_RELEASE</tt> tag for <tt>src/</tt>.</td> + </tr> + + <tr> + <td>Final builds.</td> + <td>6 May 2005</td> + <td>6 May 2005</td> + <td>Final builds for all architectures in a pristine environment.</td> + </tr> + + <tr> + <td>Warn <tt>mirror-announce@FreeBSD.org</tt></td> + <td>6 May 2005</td> + <td>6 May 2005</td> + <td>Heads up email to <a + href="mailto:mirror-announce@FreeBSD.org">mirror-announce@FreeBSD.org</a> + to give admins time to prepare for the load spike to come. The + site administrators have frequently requested advance notice for + new ISOs.</td> + </tr> + + <tr> + <td>Upload to <tt>ftp-master</tt>.</td> + <td>7 May 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 + sites and propagation of the release bits takes too long)</td> + </tr> + + <tr> + <td>Update man.cgi on the website.</td> + <td>9 May 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 + pointed to by docs.sgml.</td> + </tr> + + <tr> + <td>Announcement</td> + <td>9 May 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>17 May 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 + 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="&base;/releng/index.html">FreeBSD Release Engineering website.</a></li> +</ul> + + &footer; + + </body> +</html> |