aboutsummaryrefslogtreecommitdiff
path: root/en/releases/4.9R/qa.sgml
blob: a129cf874d6dd4d75708417bb444d8b4a698eea8 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/4.9R/qa.sgml,v 1.7 2003/10/22 13:32:25 hmp Exp $">
<!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>A bug affecting IPFW2 "limit" rules was fixed very late in
    the release cycle; other ipfw2 features should not be affected.
    We are interested in hearing any feedback about IFPW2 in
    4.9-RC3.</p></li>

  <li><p>The sysinstall(8) utility was updated to support multiple
    mail transfer agents (MTAs).  As such, the familiar Network
    Services menu was modified to expose a new option entitled
    Mail.</p><li>

  <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>

  <li><p>Users with large memory configurations (>4G) should explore
    the recently added <b>PAE</b> support in &rel;.</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>The kernel hangs solidly during device configuration when
   certain SATA controllers are installed on the system.
(<a href="http://people.FreeBSD.org/~jhb/patches/sata.patch">patch</a>)</li>

  <li>4.9-PRE panics reproducibly on a heavily loaded ata(4)-system.
   <a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/57174">PR</a></li>
</ul>

&footer;
</body>
</html>