| article.xml (258593) | article.xml (259789) |
|---|---|
| 1<?xml version="1.0" encoding="iso-8859-1"?> 2<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" 3 "../../../share/xml/freebsd50.dtd" [ 4<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "release.ent"> 5 %release; 6]> 7<!-- 8 Local Variables: --- 4 unchanged lines hidden (view full) --- 13 End: 14--> 15<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"> 16 <info><title>&os; &release.current; README</title> 17 18 19 <author><orgname>The &os; Project</orgname></author> 20 | 1<?xml version="1.0" encoding="iso-8859-1"?> 2<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" 3 "../../../share/xml/freebsd50.dtd" [ 4<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN" "release.ent"> 5 %release; 6]> 7<!-- 8 Local Variables: --- 4 unchanged lines hidden (view full) --- 13 End: 14--> 15<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"> 16 <info><title>&os; &release.current; README</title> 17 18 19 <author><orgname>The &os; Project</orgname></author> 20 |
| 21 <pubdate>$FreeBSD: stable/10/release/doc/en_US.ISO8859-1/readme/article.xml 258593 2013-11-25 20:39:09Z rodrigc $</pubdate> | 21 <pubdate>$FreeBSD: stable/10/release/doc/en_US.ISO8859-1/readme/article.xml 259789 2013-12-23 21:07:02Z gjb $</pubdate> |
| 22 23 <copyright> 24 <year>2000</year> 25 <year>2001</year> 26 <year>2002</year> 27 <year>2003</year> 28 <year>2004</year> 29 <year>2005</year> --- 77 unchanged lines hidden (view full) --- 107 ongoing development of &os;. While the &os; development team 108 tries its best to ensure that each &release.type; works as 109 advertised, &release.branch; is very much a 110 work-in-progress.</para> 111 112 <para releasetype="current">The basic requirements for using this &release.type; are 113 technical proficiency with &os; and an understanding of the 114 ongoing development process of &os; &release.branch; (as | 22 23 <copyright> 24 <year>2000</year> 25 <year>2001</year> 26 <year>2002</year> 27 <year>2003</year> 28 <year>2004</year> 29 <year>2005</year> --- 77 unchanged lines hidden (view full) --- 107 ongoing development of &os;. While the &os; development team 108 tries its best to ensure that each &release.type; works as 109 advertised, &release.branch; is very much a 110 work-in-progress.</para> 111 112 <para releasetype="current">The basic requirements for using this &release.type; are 113 technical proficiency with &os; and an understanding of the 114 ongoing development process of &os; &release.branch; (as |
| 115 discussed on the &a.current;).</para> | 115 discussed on the &a.stable;).</para> |
| 116 117 <para releasetype="current">For those more interested in doing business with &os; than 118 in experimenting with new &os; technology, formal releases 119 (such as &release.prev.stable;) are frequently more appropriate. 120 Releases undergo a period of testing and quality assurance 121 checking to ensure high reliability and dependability.</para> 122 123 <para releasetype="snapshot">This &release.type; is aimed primarily at early adopters 124 and various other users who want to get involved with the 125 ongoing development of &os;. While the &os; development team 126 tries its best to ensure that each &release.type; works as 127 advertised, &release.branch; is very much a 128 work-in-progress.</para> 129 130 <para releasetype="snapshot">The basic requirements for using this &release.type; are 131 technical proficiency with &os; and an understanding of the 132 ongoing development process of &os; &release.branch; (as | 116 117 <para releasetype="current">For those more interested in doing business with &os; than 118 in experimenting with new &os; technology, formal releases 119 (such as &release.prev.stable;) are frequently more appropriate. 120 Releases undergo a period of testing and quality assurance 121 checking to ensure high reliability and dependability.</para> 122 123 <para releasetype="snapshot">This &release.type; is aimed primarily at early adopters 124 and various other users who want to get involved with the 125 ongoing development of &os;. While the &os; development team 126 tries its best to ensure that each &release.type; works as 127 advertised, &release.branch; is very much a 128 work-in-progress.</para> 129 130 <para releasetype="snapshot">The basic requirements for using this &release.type; are 131 technical proficiency with &os; and an understanding of the 132 ongoing development process of &os; &release.branch; (as |
| 133 discussed on the &a.current;).</para> | 133 discussed on the &a.stable;).</para> |
| 134 135 <para releasetype="snapshot">For those more interested in doing business with &os; than 136 in experimenting with new &os; technology, formal releases 137 (such as &release.prev.stable;) are frequently more appropriate. 138 Releases undergo a period of testing and quality assurance 139 checking to ensure high reliability and dependability.</para> 140 141 <para releasetype="release">This &release.type; of &os; is suitable for all users. It --- 61 unchanged lines hidden (view full) --- 203 204 <sect2> 205 <title>Email and Mailing Lists</title> 206 207 <para>For any questions or general technical support issues, 208 please send mail to the &a.questions;.</para> 209 210 <para>If you're tracking the &release.branch; development efforts, you | 134 135 <para releasetype="snapshot">For those more interested in doing business with &os; than 136 in experimenting with new &os; technology, formal releases 137 (such as &release.prev.stable;) are frequently more appropriate. 138 Releases undergo a period of testing and quality assurance 139 checking to ensure high reliability and dependability.</para> 140 141 <para releasetype="release">This &release.type; of &os; is suitable for all users. It --- 61 unchanged lines hidden (view full) --- 203 204 <sect2> 205 <title>Email and Mailing Lists</title> 206 207 <para>For any questions or general technical support issues, 208 please send mail to the &a.questions;.</para> 209 210 <para>If you're tracking the &release.branch; development efforts, you |
| 211 <emphasis>must</emphasis> join the &a.current;, in order to | 211 <emphasis>must</emphasis> join the &a.stable;, in order to |
| 212 keep abreast of recent developments and changes that may 213 affect the way you use and maintain the system.</para> 214 215 <para>Being a largely-volunteer effort, the &os; 216 Project is always happy to have extra hands willing to help—there are already far more desired enhancements than 217 there is time to implement them. To contact the developers on 218 technical matters, or with offers of help, please send mail to 219 the &a.hackers;.</para> --- 194 unchanged lines hidden --- | 212 keep abreast of recent developments and changes that may 213 affect the way you use and maintain the system.</para> 214 215 <para>Being a largely-volunteer effort, the &os; 216 Project is always happy to have extra hands willing to help—there are already far more desired enhancements than 217 there is time to implement them. To contact the developers on 218 technical matters, or with offers of help, please send mail to 219 the &a.hackers;.</para> --- 194 unchanged lines hidden --- |