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

Add Robert's 4.5 Testing Guide to the web tree. Future release

Browse source 
engineering documents will probably move into this area as well.

Submitted by:	rwatson
Reviewed by:	jhb
This commit is contained in:
Murray Stokely 2002-01-12 13:29:27 +00:00
parent 729583f92f
commit f98da20e0e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=11686
3 changed files with 105 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
en/releases/4.5R/Makefile Normal file
View file

@ -0,0 +1,12 @@
# $FreeBSD$
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
.if exists(../Makefile.inc)
.include "../Makefile.inc"
.endif
DOCS= qa.sgml
.include "${WEB_PREFIX}/share/mk/web.site.mk"

91
en/releases/4.5R/qa.sgml Normal file
View file

@ -0,0 +1,91 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY title "Testing Guide for 4.5-RELEASE">
<!ENTITY email "qa">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<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 4.5-PRERELEASE 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>
<p>Features to explore carefully:</p>
<ul>
<li>Recent TCP changes, especially relating to the delayed ACK fix,
congestion response, syncache, syncookies, increased socket buffer
sizes, et al. We're interested in testing interoperability with
as many platforms as possible, demonstrating continued strong (and
better) scalability and performance, and watching out for quirks
(connection stalls, ...), not to mention crashes. Jonathan Lemon
was responding to a panic report on freebsd-current earlier today
regarding a PCB call, which is something we should keep an eye on.
On the other hand, <a href="http://www.yahoo.com">Yahoo!</a> is
now deploying this code, and that should help test it a great
deal.<br><br></li>
<li>VFS/VM/NFS fixes. We need to continue to test performance,
correctness, and interoperability. In particular, I'd like to see
a lot of inter-platform performance testing (FreeBSD->Solaris,
vice versa, etc). We'd also like careful investigation of
low-memory situations.<br><br></li>
<li>FFS fixes. We had some reports of deadlocks in FFS; it sounds like
Matt Dillon has caught most of them, but combinations I'd particular
like to see tested involve Quotas, Chroot, and NFS, under load, and
involving memory mapping and heavy directory operations.<br><br></li>
<li>NTP 4.1. This is probably reasonable safe, but it doesn't hurt
to do interop testing, especially on the Alpha platform.<br><br></li>
<li>SMBfs. We need stability testing, mostly, I suspect. Performance is
probably not a large focus. While SMBfs support has been available on
-STABLE through a port previously, determining that the integration
with the base system (especially the boot process) was done correctly
is important. Attempting to use SMBfs in /etc/fstab in a diskless
environment might be one thing to explore, for example.<br><br></li>
<li>Once the man page change goes in (which I think it should) we'll want
some basic testing of the man command.<br><br></li>
<li>cdboot. Late in the release cycle, a new implementation of the
CD-based boot loader was introduced. This should generally
improve support for booting or installing from CD, but this change
requires testing on a variety of architectures and devices.<br><br></li>
</ul>
<p>The release notes will always be a good place to look for things to
test. There are a number of new drivers, including if_em, which
would probably benefit from more exposure. Please report bugs to
the <a href="mailto:qa@FreeBSD.org">qa@FreeBSD.org</a> list, and/or
via send-pr with a heads up to the qa list.</p>
&footer;
</body>
</html>

4
en/releases/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/releases/Makefile,v 1.28 2001/04/21 07:58:29 jkh Exp $
# $FreeBSD: www/en/releases/Makefile,v 1.29 2001/09/19 08:20:45 jkh Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -11,7 +11,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
SUBDIR+= 3.3R 3.4R 3.5R 4.0R 4.1R 4.1.1R 4.2R 4.3R 4.4R 4.5R
.if defined $(NEW_BUILD)
SUBDIR=