article.xml (241096) | article.xml (250746) |
---|---|
1<?xml version="1.0" encoding="iso-8859-1" standalone="no"?> 2<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN" [ 3<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN"> 4%entities; 5 6<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> 7%release; | 1 2<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN" 3 "../../../share/xml/freebsd45.dtd" [ 4<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "release.ent"> 5 %release; |
8]> 9 10<article> 11 <articleinfo> 12 <title>&os; &release.current; README</title> 13 14 <corpauthor>The &os; Project</corpauthor> 15 | 6]> 7 8<article> 9 <articleinfo> 10 <title>&os; &release.current; README</title> 11 12 <corpauthor>The &os; Project</corpauthor> 13 |
16 <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/readme/article.xml 241096 2012-10-01 11:26:49Z gabor $</pubdate> | 14 <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/readme/article.xml 250746 2013-05-17 18:53:29Z gabor $</pubdate> |
17 18 <copyright> 19 <year>2000</year> 20 <year>2001</year> 21 <year>2002</year> 22 <year>2003</year> 23 <year>2004</year> 24 <year>2005</year> --- 62 unchanged lines hidden (view full) --- 87 commercial versions of &unix;. Most ports are also available as 88 pre-compiled <quote>packages</quote>, which can be quickly 89 installed from the installation program.</para> 90 </sect2> 91 92 <sect2> 93 <title>Target Audience</title> 94 | 15 16 <copyright> 17 <year>2000</year> 18 <year>2001</year> 19 <year>2002</year> 20 <year>2003</year> 21 <year>2004</year> 22 <year>2005</year> --- 62 unchanged lines hidden (view full) --- 85 commercial versions of &unix;. Most ports are also available as 86 pre-compiled <quote>packages</quote>, which can be quickly 87 installed from the installation program.</para> 88 </sect2> 89 90 <sect2> 91 <title>Target Audience</title> 92 |
95<![ %release.type.current; [ 96 97 <para>This &release.type; is aimed primarily at early adopters | 93 <para releasetype="current">This &release.type; is aimed primarily at early adopters |
98 and various other users who want to get involved with the 99 ongoing development of &os;. While the &os; development team 100 tries its best to ensure that each &release.type; works as 101 advertised, &release.branch; is very much a 102 work-in-progress.</para> 103 | 94 and various other users who want to get involved with the 95 ongoing development of &os;. While the &os; development team 96 tries its best to ensure that each &release.type; works as 97 advertised, &release.branch; is very much a 98 work-in-progress.</para> 99 |
104 | 100 <para releasetype="current">The basic requirements for using this &release.type; are |
105 technical proficiency with &os; and an understanding of the 106 ongoing development process of &os; &release.branch; (as 107 discussed on the &a.current;).</para> 108 | 101 technical proficiency with &os; and an understanding of the 102 ongoing development process of &os; &release.branch; (as 103 discussed on the &a.current;).</para> 104 |
109 | 105 <para releasetype="current">For those more interested in doing business with &os; than |
110 in experimenting with new &os; technology, formal releases 111 (such as &release.prev.stable;) are frequently more appropriate. 112 Releases undergo a period of testing and quality assurance 113 checking to ensure high reliability and dependability.</para> 114 | 106 in experimenting with new &os; technology, formal releases 107 (such as &release.prev.stable;) are frequently more appropriate. 108 Releases undergo a period of testing and quality assurance 109 checking to ensure high reliability and dependability.</para> 110 |
115]]> 116 117<![ %release.type.snapshot; [ 118 119 <para>This &release.type; is aimed primarily at early adopters | 111 <para releasetype="snapshot">This &release.type; is aimed primarily at early adopters |
120 and various other users who want to get involved with the 121 ongoing development of &os;. While the &os; development team 122 tries its best to ensure that each &release.type; works as 123 advertised, &release.branch; is very much a 124 work-in-progress.</para> 125 | 112 and various other users who want to get involved with the 113 ongoing development of &os;. While the &os; development team 114 tries its best to ensure that each &release.type; works as 115 advertised, &release.branch; is very much a 116 work-in-progress.</para> 117 |
126 | 118 <para releasetype="snapshot">The basic requirements for using this &release.type; are |
127 technical proficiency with &os; and an understanding of the 128 ongoing development process of &os; &release.branch; (as 129 discussed on the &a.current;).</para> 130 | 119 technical proficiency with &os; and an understanding of the 120 ongoing development process of &os; &release.branch; (as 121 discussed on the &a.current;).</para> 122 |
131 | 123 <para releasetype="snapshot">For those more interested in doing business with &os; than |
132 in experimenting with new &os; technology, formal releases 133 (such as &release.prev.stable;) are frequently more appropriate. 134 Releases undergo a period of testing and quality assurance 135 checking to ensure high reliability and dependability.</para> 136 | 124 in experimenting with new &os; technology, formal releases 125 (such as &release.prev.stable;) are frequently more appropriate. 126 Releases undergo a period of testing and quality assurance 127 checking to ensure high reliability and dependability.</para> 128 |
137]]> 138 139<![ %release.type.release; [ 140 141 <para>This &release.type; of &os; is suitable for all users. It | 129 <para releasetype="release">This &release.type; of &os; is suitable for all users. It |
142 has undergone a period of testing and quality assurance 143 checking to ensure the highest reliability and 144 dependability.</para> | 130 has undergone a period of testing and quality assurance 131 checking to ensure the highest reliability and 132 dependability.</para> |
145 146]]> 147 | |
148 </sect2> 149 </sect1> 150 151 <sect1 id="obtain"> 152 <title>Obtaining &os;</title> 153 154 <para>&os; may be obtained in a variety of ways. This section 155 focuses on those ways that are primarily useful for obtaining a --- 283 unchanged lines hidden --- | 133 </sect2> 134 </sect1> 135 136 <sect1 id="obtain"> 137 <title>Obtaining &os;</title> 138 139 <para>&os; may be obtained in a variety of ways. This section 140 focuses on those ways that are primarily useful for obtaining a --- 283 unchanged lines hidden --- |