aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHiroki Sato <hrs@FreeBSD.org>2004-08-21 12:34:42 +0000
committerHiroki Sato <hrs@FreeBSD.org>2004-08-21 12:34:42 +0000
commit8689a837cb177a2bdfcac1dd058f884f160e141d (patch)
treebab71275d90137bb2d5d3543106e8122fcb7e112
parent0dabb2c8a032abf0975eac9d91c3c58cc3bc4ae3 (diff)
Notes
-rw-r--r--release/doc/en_US.ISO8859-1/readme/article.sgml22
1 files changed, 22 insertions, 0 deletions
diff --git a/release/doc/en_US.ISO8859-1/readme/article.sgml b/release/doc/en_US.ISO8859-1/readme/article.sgml
index 5d49a50e35821..c1b55a9aae17f 100644
--- a/release/doc/en_US.ISO8859-1/readme/article.sgml
+++ b/release/doc/en_US.ISO8859-1/readme/article.sgml
@@ -86,6 +86,28 @@
<sect2>
<title>Target Audience</title>
+<![ %release.type.current; [
+
+ <para>This &release.type; is aimed primarily at early adopters
+ and various other users who want to get involved with the
+ ongoing development of &os;. While the &os; development team
+ tries its best to ensure that each &release.type; works as
+ advertised, &release.branch; is very much a
+ work-in-progress.</para>
+
+ <para>The basic requirements for using this &release.type; are
+ technical proficiency with &os; and an understanding of the
+ ongoing development process of &os; &release.branch; (as
+ discussed on the &a.current;).</para>
+
+ <para>For those more interested in doing business with &os; than
+ in experimenting with new &os; technology, formal releases
+ (such as &release.prev.stable;) are frequently more appropriate.
+ Releases undergo a period of testing and quality assurance
+ checking to ensure high reliability and dependability.</para>
+
+]]>
+
<![ %release.type.snapshot; [
<para>This &release.type; is aimed primarily at early adopters