Add a nascent testing guide for 4.8-RELEASE.

This commit is contained in:
Murray Stokely 2003-02-19 15:11:42 +00:00
parent 296ef8e3b2
commit b140a896ed
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16073

61
en/releases/4.8R/qa.sgml Normal file
View file

@ -0,0 +1,61 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY rel '4.8-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>OpenSSL. OpenSSL was updated to 0.9.7a. Please test these
things: blah foo.</p></li>
<li><p>IPFilter has recently been updated to version 3.4.XXX and has not
yet been thoroughly tested in -STABLE.</p></li>
<li><p>Firewire</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>
The QA guide is inadequate. ;)
&footer;
</body>
</html>