From owner-svn-doc-head@freebsd.org Sun Jan 10 21:25:04 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54BC8A6AB8B; Sun, 10 Jan 2016 21:25:04 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1827E1D13; Sun, 10 Jan 2016 21:25:04 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u0ALP3em066396; Sun, 10 Jan 2016 21:25:03 GMT (envelope-from rene@FreeBSD.org) Received: (from rene@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u0ALP3kF066395; Sun, 10 Jan 2016 21:25:03 GMT (envelope-from rene@FreeBSD.org) Message-Id: <201601102125.u0ALP3kF066395@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: rene set sender to rene@FreeBSD.org using -f From: Rene Ladan Date: Sun, 10 Jan 2016 21:25:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r47989 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jan 2016 21:25:04 -0000 Author: rene Date: Sun Jan 10 21:25:03 2016 New Revision: 47989 URL: https://svnweb.freebsd.org/changeset/doc/47989 Log: Synchronize the description of the intended audience of FreeBSD-STABLE with that of the Handbook. Trim section 1.7 somewhat. In section 1.9, notet that FreeBSD-STABLE is just another development branch and not specifically made for ISPs. PR: 188031 Submitted by: knl@bitflop.com Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 9 23:34:50 2016 (r47988) +++ head/en_US.ISO8859-1/books/faq/book.xml Sun Jan 10 21:25:03 2016 (r47989) @@ -346,16 +346,6 @@ is the latest release from the &rel2.stable; branch; it was released in &rel2.current.date;. - Briefly, -STABLE is aimed at the - ISP, corporate user, or any user who wants stability and a - minimal number of changes compared to the new (and - possibly unstable) features of the latest - -CURRENT snapshot. Releases can come - from either branch, but -CURRENT - is meant for users who are prepared for its increased - volatility, relative to - -STABLE. - Releases are made every few months. While many people stay more up-to-date with the &os; sources (see the questions on @@ -435,8 +425,7 @@ -CURRENT snapshot can be considered production quality for any purpose. If a stable and fully tested system is needed, - stick to full releases or use the - -STABLE snapshots. + stick to full releases. Snapshot releases are directly available from snapshot. @@ -458,11 +447,16 @@ xlink:href="&url.books.handbook;/current-stable.html#stable">-STABLE, one -CURRENT. - &os;-STABLE is intended for Internet - Service Providers and other commercial enterprises for - whom sudden shifts or experimental features are quite - undesirable. It receives only well-tested bug fixes and - other small incremental enhancements. + &os;-STABLE is the development branch + from which major releases are made. Changes go into this + branch at a slower pace and with the general assumption + that they have first been tested in &os;-CURRENT. + However, at any given time, the sources for &os;-STABLE + may or may not be suitable for general use, as it may + uncover bugs and corner cases that were not yet found in + &os;-CURRENT. Users who do not have the resources to + perform testing should instead run the most recent release + of &os;. &os;-CURRENT, on the other hand, has been one unbroken line since 2.0 was released, leading towards &rel.current;-RELEASE and beyond. For more