View | Details | Raw Unified | Return to bug 29410
Collapse All | Expand All

(-)book.sgml (-11 / +17 lines)
Lines 174-188 Link Here
174
        <answer>
174
        <answer>
175
          <para>Version <ulink
175
          <para>Version <ulink
176
            URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.3-RELEASE/">4.3</ulink>
176
            URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.3-RELEASE/">4.3</ulink>
177
            is the latest <emphasis>STABLE</emphasis> version; it was
177
            is the latest <emphasis>-RELEASE</emphasis> version; it was
178
            released in April, 2001. This is also the latest
178
            released in April, 2001. This is also the latest
179
            <emphasis>RELEASE</emphasis> version.</para>
179
            <emphasis>-SECURITY</emphasis> and <emphasis>-STABLE</emphasis> version.</para>
180
180
181
          <para>Briefly explained, <emphasis>-STABLE</emphasis> is aimed
181
          <para>Briefly explained, <emphasis>-SECURITY</emphasis>
182
            at the ISP or other corporate user who wants stability and a
182
            is aimed at all users who want highest security and stability,
183
            low change count over the wizzy new features of the latest
183
            it is <quote><emphasis>-RELEASE</emphasis> with security patches</quote>.
184
            <emphasis>-STABLE</emphasis> is aimed
185
            at users who want more new features along with stability
186
            higher than that of the latest
184
            <emphasis>-CURRENT</emphasis> snapshot.  Releases can come
187
            <emphasis>-CURRENT</emphasis> snapshot.  Releases can come
185
            from either branch, but you should only use
188
            either from <emphasis>-STABLE</emphasis> or from
189
            <emphasis>-CURRENT</emphasis> branch, but you should only use
186
            <emphasis>-CURRENT</emphasis> if you are sure that you are
190
            <emphasis>-CURRENT</emphasis> if you are sure that you are
187
            prepared for its increased volatility (relative to
191
            prepared for its increased volatility (relative to
188
            <emphasis>-STABLE</emphasis>, that is).</para>
192
            <emphasis>-STABLE</emphasis>, that is).</para>
Lines 204-215 Link Here
204
208
205
        <answer>
209
        <answer>
206
          <para><ulink
210
          <para><ulink
207
            URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink>
211
            URL="../handbook/cutting-edge.html">FreeBSD-CURRENT</ulink>
208
            is the development version of the operating system, which will
212
            is the development version of the operating system, which will
209
            in due course become 5.0-RELEASE.  As such, it is really only
213
            in due course become 5.0-RELEASE.  As such, it is really only
210
            of interest to developers working on the system and die-hard
214
            of interest to developers working on the system and die-hard
211
            hobbyists.  See the <ulink
215
            hobbyists.  See the <ulink
212
            URL="../handbook/cutting-edge.html#CURRENT">relevant
216
            URL="../handbook/cutting-edge.html">relevant
213
            section</ulink> in the <ulink
217
            section</ulink> in the <ulink
214
            URL="../handbook/index.html">handbook</ulink> for details on
218
            URL="../handbook/index.html">handbook</ulink> for details on
215
            running -CURRENT.</para>
219
            running -CURRENT.</para>
Lines 287-302 Link Here
287
        <answer>
291
        <answer>
288
          <para>Back when FreeBSD 2.0.5 was released, we decided to
292
          <para>Back when FreeBSD 2.0.5 was released, we decided to
289
            branch FreeBSD development into two parts.  One branch was
293
            branch FreeBSD development into two parts.  One branch was
290
            named <ulink URL="../handbook/stable.html">-STABLE</ulink>,
294
            <ulink URL="../handbook/cutting-edge.html">named</ulink> -STABLE,
291
            with the intention that only well-tested bug fixes and small
295
            with the intention that only well-tested bug fixes and small
292
            incremental enhancements would be made to it (for Internet
296
            incremental enhancements would be made to it (for Internet
293
            Service Providers and other commercial enterprises for whom
297
            Service Providers and other commercial enterprises for whom
294
            sudden shifts or experimental features are quite
298
            sudden shifts or experimental features are quite
295
            undesirable).  The other branch was <ulink
299
            undesirable).  The other branch was -CURRENT,
296
            URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>,
297
            which essentially has been one unbroken line leading towards
300
            which essentially has been one unbroken line leading towards
298
            5.0-RELEASE (and beyond) since 2.0 was released. If a little
301
            5.0-RELEASE (and beyond) since 2.0 was released. If a little
299
            ASCII art would help, this is how it looks:</para>
302
            ASCII art would help, this is how it looks:</para>
303
          <para>With release of FreeBSD 4.3 a new <emphasis>-SECURITY</emphasis> branch was
304
            introduced, which is a <quote>-RELEASE with security 
305
            patches</quote>.</para>
300
306
301
          <programlisting>                 2.0
307
          <programlisting>                 2.0
302
                  |
308
                  |

Return to bug 29410