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

Add preliminary schedule, etc, for 4.10R

Browse source
This commit is contained in:
Scott Long 2004-03-29 23:18:19 +00:00
parent 7f4828b08d
commit e360796278
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=20439
8 changed files with 646 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
en/releases/4.10R/Makefile Normal file
View file

@ -0,0 +1,14 @@
# $FreeBSD: www/en/releases/4.9R/Makefile,v 1.4 2003/10/29 07:30:30 murray Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
.if exists(../Makefile.inc)
.include "../Makefile.inc"
.endif
DOCS= hardware.sgml relnotes.sgml schedule.sgml todo.sgml qa.sgml
DATA= docbook.css
.include "${WEB_PREFIX}/share/mk/web.site.mk"

165
en/releases/4.10R/docbook.css Normal file
View file

@ -0,0 +1,165 @@
/*
* Copyright (c) 2001, 2003 The FreeBSD Documentation Project
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* $FreeBSD: doc/share/misc/docbook.css,v 1.6 2003/07/10 15:25:35 blackend Exp $
*/
BODY ADDRESS {
line-height: 1.3;
margin: .6em 0;
}
BODY BLOCKQUOTE {
margin-top: .75em;
line-height: 1.5;
margin-bottom: .75em;
}
HTML BODY {
margin: 1em 8% 1em 10%;
line-height: 1.2;
}
.LEGALNOTICE {
font-size: small;
font-variant: small-caps;
}
BODY DIV {
margin: 0;
}
DL {
margin: .8em 0;
line-height: 1.2;
}
BODY FORM {
margin: .6em 0;
}
H1, H2, H3, H4, H5, H6,
DIV.EXAMPLE P B,
.QUESTION,
DIV.TABLE P B,
DIV.PROCEDURE P B {
color: #990000;
}
BODY H1 {
margin: .8em 0 0 -4%;
line-height: 1.3;
}
BODY H2 {
margin: .8em 0 0 -4%;
line-height: 1.3;
}
BODY H3 {
margin: .8em 0 0 -3%;
line-height: 1.3;
}
BODY H4 {
margin: .8em 0 0 -3%;
line-height: 1.3;
}
BODY H5 {
margin: .8em 0 0 -2%;
line-height: 1.3;
}
BODY H6 {
margin: .8em 0 0 -1%;
line-height: 1.3;
}
BODY HR {
margin: .6em
}
BODY IMG.NAVHEADER {
margin: 0 0 0 -4%;
}
OL {
margin: 0 0 0 5%;
line-height: 1.2;
}
BODY P {
margin: .6em 0;
line-height: 1.2;
}
BODY PRE {
margin: .75em 0;
line-height: 1.0;
color: #461b7e;
}
BODY TD {
line-height: 1.2
}
BODY TH {
line-height: 1.2;
}
UL, BODY DIR, BODY MENU {
margin: 0 0 0 5%;
line-height: 1.2;
}
HTML {
margin: 0;
padding: 0;
}
.FILENAME {
color: #007a00;
}
BODY H1, BODY H2, BODY H3, BODY H4, BODY H5, BODY H6 {
margin-left: 0
}
.GUIMENU, .GUIMENUITEM, .GUISUBMENU,
.GUILABEL, .INTERFACE, .GUIBUTTON,
.SHORTCUT, .SHORTCUT .KEYCAP {
background-color: #F0F0F0;
}
.ACCEL {
background-color: #F0F0F0;
text-decoration: underline;
}
.PROGRAMLISTING, .SCREEN {
margin-left: 3ex;
}

26
en/releases/4.10R/hardware.sgml Normal file
View file

@ -0,0 +1,26 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY title "FreeBSD 4.10-RELEASE Hardware Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<p>The hardware notes for FreeBSD are customized for different
platforms, as some of the changes made to FreeBSD apply only to
specific processor architectures.</p>
<p>Hardware notes for FreeBSD 4.10-RELEASE are available for the following
platforms:</p>
<ul>
<li><a href="hardware-i386.html">i386</a></li>
<li><a href="hardware-alpha.html">Alpha</a></li>
</ul>
<p>A list of all platforms currently under development can be found
on the <a href="../../platforms/index.html">Supported
Platforms</a> page.</p>
</html>

57
en/releases/4.10R/qa.sgml Normal file
View file

@ -0,0 +1,57 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY rel '4.10-RELEASE'>
<!ENTITY title "Testing Guide for &rel;">
<!ENTITY email "qa">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<h3>Goals</h3>
<p>As part of our on-going effort to improve the release engineering
process, we have identified several areas that need significant
quality assurance testing during the release candidate phase.
Below, we've listed the changes in &rel; that we feel merit
the most attention due to their involving substantial changes to the
system, or having arrived late in the development cycle leading up
to the release. In general, our goal in the QA process is to
attempt to check a number of things:</p>
<ul>
<li>The system has not regressed with respects to stability, correctness,
interoperability, or performance of features present in prior
releases.<br><br></li>
<li>New features result in the desired improvement in stability,
correctness, interoperability, or performance.</li>
</ul>
<p>To effectively determine this, it's desirable to test the system in
a diverse set of environments, applying a wide set of workloads,
forcing the system to operate both within and outside its normal
specification. Particular focus should often be placed on the
continuing (or new) capability of the system to perform correctly
when used in concert with systems from other vendors.</p>
<h3>Features to explore carefully:</h3>
<ul>
<li>There was a large merge of the USB code from RELENG_5 into RELENG_4.
This requires as much testing as possible to make sure that no devices
have regressed in stability or functionality.
</ul>
<p>The <a href="../../relnotes.html">release notes</a> will always be
a good place to look for things to test.</p>
<h3>Known Issues</h3>
<ul>
<li>No known issues at this time.
</ul>
&footer;
</body>
</html>

26
en/releases/4.10R/relnotes.sgml Normal file
View file

@ -0,0 +1,26 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/4.9R/relnotes.sgml,v 1.1 2003/10/23 18:52:26 bmah Exp $">
<!ENTITY title "FreeBSD 4.9-RELEASE Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<p>The release notes for FreeBSD are customized for different
platforms, as some of the changes made to FreeBSD apply only to
specific processor architectures.</p>
<p>Release notes for FreeBSD 4.9-RELEASE are available for the following
platforms:</p>
<ul>
<li><a href="relnotes-i386.html">i386</a></li>
<li><a href="relnotes-alpha.html">Alpha</a></li>
</ul>
<p>A list of all platforms currently under development can be found
on the <a href="../../platforms/index.html">Supported
Platforms</a> page.</p>
</html>

283
en/releases/4.10R/schedule.sgml Normal file
View file

@ -0,0 +1,283 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!ENTITY local.rel "4.10">
<!ENTITY local.rel.tag "4_10">
<!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>30&nbsp;Mar&nbsp;2004</td>
<td>--</td>
<td>Release Engineers send announcement email to
<tt>developers@FreeBSD.org</tt> with a rough schedule for the FreeBSD
&local.rel; release.</td>
</tr>
<tr>
<td>&local.rel;-BETA Testing Guide published</td>
<td>30&nbsp;Mar&nbsp;2004</td>
<td>--</td>
<td>A <a href="&base;/releases/&local.rel;R/qa.html">testing guide</a>
should be published with information about recent changes and
areas of the system that should be thoroughly tested during the
pre-release/RC period.</td>
</tr>
<tr>
<td>Announce the Ports Freeze</td>
<td>--</td>
<td>--</td>
<td>Someone from <tt>portmgr@</tt> should email
<tt>freebsd-ports@</tt> and BCC: <tt>developers@</tt> to set a date
for the week long ports freeze and tagging of the ports tree.</td>
</tr>
<tr>
<td><tt>&local.rel;-BETA</tt></td>
<td>7&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td><tt>newvers.sh</tt>, and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>7&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td>After this date, all commits to the <tt>RELENG_4</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 <tt>developers@</tt>, <tt>stable@</tt>
and <tt>qa@</tt> lists.</td>
</tr>
<tr>
<td><tt>RELENG_&local.rel.tag;</tt> branch</td>
<td>20&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td>The release branch is created.</td>
</tr>
<tr>
<td>Unfreeze the tree</td>
<td>20&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td>Announcement to <tt>developers@</tt> explaining that the release is
out, and commits to <tt>RELENG_4</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;-RC</tt></td>
<td>20&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td><tt>newvers.sh</tt> and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>First release candidate</td>
<td>21&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td>The first release candidate for the x86 and Alpha 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 end 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>21&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the snapshot is uploaded.</td>
</tr>
<tr>
<td>Second release candidate</td>
<td>27&nbsp;Apr&nbsp;2004</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>28&nbsp;Apr&nbsp;2004</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the snapshot is uploaded.</td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<tr>
<td>Ports tree frozen</td>
<td>--</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>Announce <tt>doc/</tt> tree slush</td>
<td>--</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>--</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>
<!-- 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>--</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>--</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>--</td>
<td>--</td>
<td>The ports cluster and <a href="http://bento.FreeBSD.org">bento</a>
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>--</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>4&nbsp;May&nbsp;2004</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 the fact that this is FreeBSD &local.rel;.</td>
</tr>
<tr>
<td>Update man.cgi on the website.</td>
<td>4&nbsp;May&nbsp;2004</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>src tree tagged.</td>
<td>4&nbsp;May&nbsp;2004</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>4&nbsp;May&nbsp;2004</td>
<td>--</td>
<td>Final builds for x86 and Alpha in a pristine environment.</td>
</tr>
<tr>
<td>Warn <tt>mirror-announce@FreeBSD.org</tt></td>
<td>4&nbsp;May&nbsp;2004</td>
<td>--</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>4&nbsp;May&nbsp;2004</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>Announcement</td>
<td>5&nbsp;May&nbsp;2004</td>
<td>--</td>
<td>Announcement sent out after a majority of the mirrors have
received the bits.</td>
</tr>
</table>
<h1>Additional Information</h1>
<ul>
<li><a href="todo.html">FreeBSD &local.rel; developer todo list.</a></li>
<li><a href="qa.html">FreeBSD &local.rel; Quality Assurance Guide.</a></li>
<li><a href="&base;/releng/index.html">FreeBSD Release Engineering website.</a></li>
<li><a href="&base;/projects/busdma/index.html">FreeBSD busdma driver project page.</a></li>
</ul>
&footer;
</body>
</html>

73
en/releases/4.10R/todo.sgml Normal file
View file

@ -0,0 +1,73 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!ENTITY local.rel "4.10">
<!ENTITY title "FreeBSD &local.rel; Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
<!ENTITY status.na "<font color=green>N/A</font>">
<!ENTITY status.done "<font color=green>Done</font>">
<!ENTITY status.wip "<font color=blue>In&nbsp;progress</font>">
<!ENTITY status.untested "<font color=orange>Needs&nbsp;testing</font>">
<!ENTITY status.new "<font color=red>Not&nbsp;done</font>">
<!ENTITY status.unknown "<font color=red>Unknown</font>">
]>
<html>
&header;
<h1>Open Issues</h1>
<p>This is a list of open issues that need to be resolved for FreeBSD
&local.rel;. If you have any updates for this list, please e-mail
re@FreeBSD.org.</p>
<p>As many of these open issues involve merging bus_dma driver changes
from -CURRENT, the <a
href="&base;/projects/busdma/index.html">busdma</a> project page is
also useful.</p>
<h3>Must Resolve Issues for &local.rel;-RC3</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
</table>
<h3>Must Resolve Issues for &local.rel;-RELEASE</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
</table>
<h3>Desired Features for &local.rel;-RELEASE</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
</table>
<h3>Documentation items that must be resolved for &local.rel;</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
</table>
<h3>Testing focuses for &local.rel;</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
</table>
&footer;
</body>
</html>

4
en/releases/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/releases/Makefile,v 1.40 2004/01/14 06:12:54 scottl Exp $
# $FreeBSD: www/en/releases/Makefile,v 1.41 2004/02/25 05:10:01 bmah Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -12,7 +12,7 @@ DOCS?= index.sgml snapshots.sgml
SUBDIR= 1.1 1.1.5 2.0 2.0.5R 2.1R 2.1.5R 2.1.6R 2.1.7R 2.2R
SUBDIR+= 2.2.1R 2.2.2R 2.2.5R 2.2.6R 2.2.7R 2.2.8R 3.0R 3.1R 3.2R
SUBDIR+= 3.3R 3.4R 3.5R 4.0R 4.1R 4.1.1R 4.2R 4.3R 4.4R 4.5R 4.6R
SUBDIR+= 4.6.2R 4.7R 4.8R 4.9R
SUBDIR+= 4.6.2R 4.7R 4.8R 4.9R 4.10R
SUBDIR+= 5.0R 5.1R 5.2R 5.2.1R 5.3R
.if defined $(NEW_BUILD)