Initial pass at a schedule for the 6.0 release. Very vague at the moment,

many dates need to be decided later.
This commit is contained in:
Ken Smith 2005-06-10 14:23:55 +00:00
parent 92d648dac3
commit 61957d1f81
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=24804
2 changed files with 182 additions and 2 deletions

View file

@ -1,4 +1,4 @@
# $FreeBSD$
# $FreeBSD: www/en/releases/6.0R/Makefile,v 1.1 2004/10/22 09:49:00 rwatson Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -7,7 +7,7 @@
.include "../Makefile.inc"
.endif
DOCS= todo.sgml
DOCS= todo.sgml schedule.sgml
DATA= docbook.css

View file

@ -0,0 +1,180 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!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 border=1>
<tr>
<td>Action</td>
<td>Expected</td>
<td>Actual</td>
<td>Description</td>
</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>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="&base;/releng/index.html">FreeBSD Release Engineering website.</a></li>
</ul>
&footer;
</body>
</html>