diff --git a/en/releases/4.6R/Makefile b/en/releases/4.6R/Makefile
index dfa73009dc..9c66c1ff15 100644
--- a/en/releases/4.6R/Makefile
+++ b/en/releases/4.6R/Makefile
@@ -1,12 +1,12 @@
-# $FreeBSD$
+# $FreeBSD: www/en/releases/4.6R/Makefile,v 1.1 2002/01/30 04:55:06 murray Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
.if exists(../Makefile.inc)
.include "../Makefile.inc"
.endif
-DOCS= schedule.sgml
+DOCS= qa.sgml schedule.sgml
.include "${WEB_PREFIX}/share/mk/web.site.mk"
diff --git a/en/releases/4.6R/qa.sgml b/en/releases/4.6R/qa.sgml
new file mode 100644
index 0000000000..4172deee42
--- /dev/null
+++ b/en/releases/4.6R/qa.sgml
@@ -0,0 +1,59 @@
+
+
+
+
+ %includes;
+]>
+
+&header;
+
+Goals
+
+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.6-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:
+
+
+ - The system has not regressed with respects to stability, correctness,
+ interoperability, or performance of features present in prior
+ releases.
+
+ - New features result in the desired improvement in stability,
+ correctness, interoperability, or performance.
+
+
+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.
+
+Features to explore carefully:
+
+
+
+ - DHCP client support. This release will feature a major update
+ of the ISC DHCP client (v3.0.1 RC8). The common cases have been
+ well tested, but testing in more demanding or unusual environments
+ would be beneficial. In particular, the new dynamic DNS update
+ functionality has not been well tested.
+
+
+
+The release notes will always be
+ a good place to look for things to test.
+
+Known Issues
+
+None at this time.
+
+&footer;
+
+