os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add release schedule pages for 6.1R and 5.5R.

Browse source
This commit is contained in:
Hiroki Sato 2006-02-12 15:36:17 +00:00
parent e3c2fcc58a
commit fa61c2f948
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=27097
4 changed files with 594 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
en/releases/5.5R/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD$
# $FreeBSD: www/en/releases/5.5R/Makefile,v 1.1 2006/01/26 00:10:24 murray Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -8,5 +8,6 @@
.endif
DOCS= todo.sgml approvals.sgml
DOCS+= schedule.sgml
.include "${WEB_PREFIX}/share/mk/web.site.mk"

303
en/releases/5.5R/schedule.sgml Normal file
View file

@ -0,0 +1,303 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!ENTITY local.rel "5.5">
<!ENTITY local.rel.tag "5_5">
<!ENTITY title "FreeBSD &local.rel; Release Process">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
<!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 class="tblbasic">
<tr class="heading">
<th>Action</th>
<th>Expected</th>
<th>Actual</th>
<th>Description</th>
</tr>
<tr>
<td>Reminder announcement</td>
<td>--</td>
<td>25&nbsp;January&nbsp;2006</td>
<td>Release Engineers send announcement email to
developers with a rough schedule for the FreeBSD
&local.rel; release.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>31&nbsp;January&nbsp;2006</td>
<td>31&nbsp;January&nbsp;2006</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>
<tr>
<td>Announce the Ports Freeze</td>
<td>--</td>
<td>5&nbsp;February&nbsp;2006</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>Begin <tt>&local.rel;-BETA1</tt> builds</td>
<td>5&nbsp;February&nbsp;2006</td>
<td>5&nbsp;February&nbsp;2006</td>
<td>Begin building the first public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA1</tt></td>
<td>5&nbsp;February&nbsp;2006</td>
<td>5&nbsp;February&nbsp;2006</td>
<td>&local.rel;-BETA1 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-BETA2</tt> builds</td>
<td>19&nbsp;February&nbsp;2006</td>
<td>--</td>
<td>Begin building the second public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA2</tt></td>
<td>19&nbsp;February&nbsp;2006</td>
<td>--</td>
<td>&local.rel;-BETA2 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<tr>
<td>Ports tree frozen</td>
<td>20&nbsp;February&nbsp;2006</td>
<td>--</td>
<td>Only approved commits will be permitted to the <tt>ports/</tt>
tree during the freeze.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-BETA3</tt> builds</td>
<td>5&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Begin building the third public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA3</tt></td>
<td>5&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>&local.rel;-BETA2 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>6&nbsp;March&nbsp;2006</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 -->
<!-- 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>6&nbsp;March&nbsp;2006</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>6&nbsp;March&nbsp;2006</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>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree slush</td>
<td>10&nbsp;March&nbsp;2006</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>13&nbsp;March&nbsp;2006</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_5_5</tt> branch</td>
<td>19&nbsp;March&nbsp;2006</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>src/</tt> unfrozen</td>
<td>TBD</td>
<td>--</td>
<td>Unfreeze <tt>RELENG_5</tt> src. Continue to coordinate significant
check-ins with <tt>re@FreeBSD.org</tt> until the release is final.</td>
</tr>
<tr>
<td>Build <tt>&local.rel;-RC1</tt></td>
<td>19&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Begin building the first release candidate build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-RC1</tt></td>
<td>19&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>&local.rel;-RC1 tier-1 platform images released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<tr>
<td>Build <tt>&local.rel;-RC2</tt></td>
<td>26&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Begin building the second release candidate build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-RC2</tt></td>
<td>26&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>&local.rel;-RC2 tier-1 platform images released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<tr>
<td>Version numbers bumped</td>
<td>31&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>The files listed <a
href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">here</a>
are updated to reflect FreeBSD &local.rel;.</td>
</tr>
<tr>
<td><tt>src/</tt> tree tagged</td>
<td>31&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Tag the <tt>RELENG_&local.rel.tag;</tt> branch with
<tt>RELENG_&local.rel.tag;_0_RELEASE</tt>.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-RELEASE</tt> builds</td>
<td>31&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Start &local.rel;-RELEASE Tier-1 builds.</td>
</tr>
<tr>
<td>Warn <tt>mirror-announce@FreeBSD.org</tt></td>
<td>31&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Heads up email to <tt>mirror-announce@FreeBSD.org</tt> 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>2&nbsp;April&nbsp;2006</td>
<td>--</td>
<td>Release and packages uploaded to <tt>ftp-master.FreeBSD.org.</tt></td>
</tr>
<tr>
<td>Announcement</td>
<td>3&nbsp;April&nbsp;2006</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>

3
en/releases/6.1R/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD$
# $FreeBSD: www/en/releases/6.1R/Makefile,v 1.1 2006/01/25 23:58:36 murray Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -8,6 +8,7 @@
.endif
DOCS= todo.sgml approvals.sgml
DOCS+= schedule.sgml
FETCHFILE= http://people.freebsd.org/~pho/stress/log/news.rdf
FETCHCMD= /usr/bin/fetch

287
en/releases/6.1R/schedule.sgml Normal file
View file

@ -0,0 +1,287 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!ENTITY local.rel "6.1">
<!ENTITY local.rel.tag "6_1">
<!ENTITY title "FreeBSD &local.rel; Release Process">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
<!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 class="tblbasic">
<tr class="heading">
<th>Action</th>
<th>Expected</th>
<th>Actual</th>
<th>Description</th>
</tr>
<tr>
<td>Reminder announcement</td>
<td>--</td>
<td>25&nbsp;January&nbsp;2006</td>
<td>Release Engineers send announcement email to
developers with a rough schedule for the FreeBSD
&local.rel; release.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>31&nbsp;January&nbsp;2006</td>
<td>31&nbsp;January&nbsp;2006</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>
<tr>
<td>Announce the Ports Freeze</td>
<td>--</td>
<td>5&nbsp;February&nbsp;2006</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>Begin <tt>&local.rel;-BETA1</tt> builds</td>
<td>5&nbsp;February&nbsp;2006</td>
<td>5&nbsp;February&nbsp;2006</td>
<td>Begin building the first public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA1</tt></td>
<td>5&nbsp;February&nbsp;2006</td>
<td>5&nbsp;February&nbsp;2006</td>
<td>&local.rel;-BETA1 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-BETA2</tt> builds</td>
<td>19&nbsp;February&nbsp;2006</td>
<td>--</td>
<td>Begin building the second public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA2</tt></td>
<td>19&nbsp;February&nbsp;2006</td>
<td>--</td>
<td>&local.rel;-BETA2 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<tr>
<td>Ports tree frozen</td>
<td>20&nbsp;February&nbsp;2006</td>
<td>--</td>
<td>Only approved commits will be permitted to the <tt>ports/</tt>
tree during the freeze.</td>
</tr>
<tr>
<td><tt>RELENG_6_1</tt> branch</td>
<td>5&nbsp;March&nbsp;2006</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>src/</tt> unfrozen</td>
<td>TBD</td>
<td>--</td>
<td>Unfreeze <tt>RELENG_6</tt> src. Continue to coordinate significant
check-ins with <tt>re@FreeBSD.org</tt> until the release is final.</td>
</tr>
<tr>
<td>Build <tt>&local.rel;-RC1</tt></td>
<td>5&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Begin building the first release candidate build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-RC1</tt></td>
<td>5&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>&local.rel;-RC1 tier-1 platform images released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</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>6&nbsp;March&nbsp;2006</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>6&nbsp;March&nbsp;2006</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>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>6&nbsp;March&nbsp;2006</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>
<td>10&nbsp;March&nbsp;2006</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>
<tr>
<td>Build <tt>&local.rel;-RC2</tt></td>
<td>12&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Begin building the second release candidate build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-RC2</tt></td>
<td>12&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>&local.rel;-RC2 tier-1 platform images released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree tagged.</td>
<td>13&nbsp;March&nbsp;2006</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>Version numbers bumped</td>
<td>17&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>The files listed <a
href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">here</a>
are updated to reflect FreeBSD &local.rel;.</td>
</tr>
<tr>
<td><tt>src/</tt> tree tagged</td>
<td>17&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Tag the <tt>RELENG_&local.rel.tag;</tt> branch with
<tt>RELENG_&local.rel.tag;_0_RELEASE</tt>.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-RELEASE</tt> builds</td>
<td>17&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Start &local.rel;-RELEASE Tier-1 builds.</td>
</tr>
<tr>
<td>Warn <tt>mirror-announce@FreeBSD.org</tt></td>
<td>17&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Heads up email to <tt>mirror-announce@FreeBSD.org</tt> 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>19&nbsp;March&nbsp;2006</td>
<td>--</td>
<td>Release and packages uploaded to <tt>ftp-master.FreeBSD.org.</tt></td>
</tr>
<tr>
<td>Announcement</td>
<td>20&nbsp;March&nbsp;2006</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>