MFP4: FreeBSD 4.9 Release Schedule and nascent todo/qa guides.

This commit is contained in:
Murray Stokely 2003-08-18 19:43:46 +00:00
parent a46f4884bc
commit 2e30180ff6
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=17906
4 changed files with 207 additions and 28 deletions

View file

@ -1,4 +1,4 @@
# $FreeBSD$
# $FreeBSD: www/en/releases/4.9R/Makefile,v 1.1 2003/05/06 04:40:43 murray Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -7,6 +7,6 @@
.include "../Makefile.inc"
.endif
DOCS= schedule.sgml
DOCS= schedule.sgml todo.sgml qa.sgml
.include "${WEB_PREFIX}/share/mk/web.site.mk"

57
en/releases/4.9R/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.9-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><p>The <tt>xl</tt> driver has recently been updated with full
busdma support among other improvements. This driver will now
work with large memory systems with PAE enabled.</p></li>
</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>None at this time.</li>
</ul>
&footer;
</body>
</html>

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$">
<!ENTITY date "$FreeBSD: www/en/releases/4.9R/schedule.sgml,v 1.1 2003/05/06 04:40:43 murray Exp $">
<!ENTITY local.rel "4.9">
<!ENTITY local.rel.tag "4_9">
<!ENTITY title "FreeBSD &local.rel; Release Process">
@ -33,26 +33,26 @@
</tr>
<tr>
<td>Reminder announcement</td>
<td>TBD</td>
<td>--</td>
<td>28&nbsp;Jul&nbsp;2003</td>
<td>28&nbsp;Jul&nbsp;2003</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>Another Reminder announcement</td>
<td>TBD</td>
<td>18&nbsp;Aug&nbsp;2003</td>
<td>--</td>
<td>1 week reminder.</td>
</tr>
<tr>
<td>Another Reminder announcement</td>
<td>TBD</td>
<td>22&nbsp;Aug&nbsp;2003</td>
<td>--</td>
<td>Final reminder, with exact time (GMT) that freeze begins.</td>
</tr>
<tr>
<td>&local.rel;-PRERELEASE Testing Guide published</td><td>TBD</td><td>--</td>
<td>&local.rel;-PRERELEASE Testing Guide published</td><td>25 Aug 2003</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
@ -60,19 +60,19 @@
</tr>
<tr>
<td><tt>&local.rel;-PRERELEASE</tt></td>
<td>TBD</td>
<td>25 Aug 2003</td>
<td>--</td>
<td><tt>newvers.sh</tt>, and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>FTP site updated</td>
<td>TBD</td>
<td>25 Aug 2003</td>
<td>--</td>
<td><tt>pkg_add -r</tt> works for <tt>&local.rel;-PRERELEASE</tt> machines.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>TBD</td>
<td>25 Aug 2003</td>
<td>--</td>
<td>After this date, all commits to the <tt>RELENG_4</tt> branch
@ -85,7 +85,7 @@
<tr>
<td><tt>&local.rel;-RC</tt></td>
<td>TBD</td>
<td>12 Sep 2003</td>
<td>--</td>
<td><tt>newvers.sh</tt> and <tt>release.ent</tt> updated.</td>
</tr>
@ -101,7 +101,7 @@
<tr>
<td>First release candidate</td>
<td>TBD</td>
<td>12 Sep 2003</td>
<td>--</td>
<td>The first release candidate for the x86 and Alpha architecture is
released. ISO images should be uploaded to
@ -114,7 +114,7 @@
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>TBD</td>
<td>12 Sep 2003</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>
@ -122,7 +122,7 @@
<tr>
<td>Second release candidate</td>
<td>TBD</td>
<td>17 Sep 2003</td>
<td>--</td>
<td>Note: the release date of this candidate depends on the user
experience with RC1.</td>
@ -130,7 +130,7 @@
<tr>
<td>Third release candidate</td>
<td>TBD</td>
<td>22 Sep 2003</td>
<td>--</td>
<td></td>
</tr>
@ -183,7 +183,7 @@
<tr>
<td>Final package build starts
<td>TBD</td>
<td>22 Sep 2003</td>
<td>--</td>
<td>The ports cluster and <a href="http://bento.FreeBSD.org">bento</a>
build final packages.</td>
@ -192,7 +192,7 @@
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree tagged.</td>
<td>TBD</td>
<td>22 Sep 2003</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>
@ -201,14 +201,14 @@
<tr>
<td><tt>RELENG_&local.rel.tag;</tt> branch</td>
<td>TBD</td>
<td>23 Sep 2003</td>
<td>--</td>
<td>The release branch is created.</td>
</tr>
<tr>
<td>Note to freebsd-stable@</td>
<td>TBD</td>
<td>24 Sep 2003</td>
<td>--</td>
<td>A note should be sent to the freebsd-stable@ list to let
over-anxious users know that the tags have been created but the
@ -219,7 +219,7 @@
<tr>
<td>Version numbers bumped.</td>
<td>TBD</td>
<td>24 Sep 2003</td>
<td>--</td>
<td>The files listed <a
href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">here</a>
@ -228,7 +228,7 @@
<tr>
<td>Update man.cgi on the website.</td>
<td>TBD</td>
<td>25 Sep 2003</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
@ -237,21 +237,21 @@
<tr>
<td>src tree tagged.</td>
<td>TBD</td>
<td>25 Sep 2003</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>TBD</td>
<td>25 Sep 2003</td>
<td>--</td>
<td>Final builds for x86 and Alpha in a pristine environment.</td>
</tr>
<tr>
<td>Warn <tt>hubs@FreeBSD.org</tt></td>
<td>TBD</td>
<td>25 Sep 2003</td>
<td>--</td>
<td>Heads up email to <a
href="mailto:hubs@FreeBSD.org">hubs@FreeBSD.org</a> to give admins
@ -262,14 +262,14 @@
<tr>
<td>Upload to <tt>ftp-master</tt>.</td>
<td>TBD</td>
<td>26 Sep 2003</td>
<td>--</td>
<td>Release and packages uploaded to <tt>ftp-master.FreeBSD.org</tt></td>
</tr>
<tr>
<td>Announcement</td>
<td>TBD</td>
<td>29 Sep 2003</td>
<td>--</td>
<td>Announcement sent out after a majority of the mirrors have
received the bits.</td>
@ -277,7 +277,7 @@
<tr>
<td>Unfreeze the tree</td>
<td>TBD</td>
<td>29 Sep 2003</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

122
en/releases/4.9R/todo.sgml Normal file
View file

@ -0,0 +1,122 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!ENTITY local.rel "4.9">
<!ENTITY title "FreeBSD &local.rel; Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
]>
<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>
<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>
<tr>
<td>if_dc tested/merged to work with PAE in 4.x</td>
<td>--</td>
<td>luoqi</td>
<td></td>
</tr>
<tr>
<td>busdma infrastructure merges</td>
<td>--</td>
<td>scottl</td>
<td>It's unclear if further bus_dma infrastructure changes need to be merged?</td>
</tr>
<tr>
<td>if_xl</td>
<td>Done</td>
<td>silby</td>
<td></td>
</tr>
<tr>
<td>RAID drivers tested/merged to work with PAE in 4.x</td>
<td>--</td>
<td>scottl</td>
<td></td>
</tr>
<tr>
<td>ACPI merged as optional component</td>
<td>In progress</td>
<td>&a.jhb;</td>
<td>ACPI will be provided as an optional component, turned off by
default.</td>
</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>
<tr>
<td>USB updated to work with PAE</td>
<td>In progress</td>
<td>jmg, joe, luoqi</td>
<td>USB does not currently work with PAE enabled.</td>
</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>
<tr>
<td>ACPI</td>
<td>--</td>
<td>Murray</td>
<td>Handbook should be updated to note that ACPI can be enabled on
4.9 systems.</td>
</tr>
<tr>
<td>PAE</td>
<td>--</td>
<td>Murray</td>
<td>Handbook should be updated to explain the basic PAE functionality.</td>
</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>
<tr>
<td>PAE testing</td>
<td>--</td>
<td>More testing should be done with PAE systems to test device
compatibility and performance. In particular, active systems
with 12 gig of ram or more should be thoroughly tested to make
sure the various memory allocation algorithms in the kernel
still scale properly. There were reports of users running out of
KVA space in -CURRENT with large memory machines.</td>
</tr>
</table>
&footer;
</body>
</html>