From owner-svn-doc-all@freebsd.org Fri Feb 9 20:33:21 2018 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37BA6F21F59; Fri, 9 Feb 2018 20:33:21 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D421A77F2B; Fri, 9 Feb 2018 20:33:20 +0000 (UTC) (envelope-from wblock@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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CEE6F1C64; Fri, 9 Feb 2018 20:33:20 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w19KXKph064404; Fri, 9 Feb 2018 20:33:20 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w19KXKon064403; Fri, 9 Feb 2018 20:33:20 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201802092033.w19KXKon064403@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Fri, 9 Feb 2018 20:33:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51412 - head/en_US.ISO8859-1/books/handbook/cutting-edge X-SVN-Group: doc-head X-SVN-Commit-Author: wblock X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/handbook/cutting-edge X-SVN-Commit-Revision: 51412 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2018 20:33:21 -0000 Author: wblock Date: Fri Feb 9 20:33:20 2018 New Revision: 51412 URL: https://svnweb.freebsd.org/changeset/doc/51412 Log: Restore the Using FreeBSD-Stable section, which somehow got accidentally deleted ten months ago and nobody noticed until now. Reported by: AMDmi3 on IRC Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Fri Feb 9 17:19:21 2018 (r51411) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Fri Feb 9 20:33:20 2018 (r51412) @@ -1067,6 +1067,98 @@ before running "/usr/sbin/freebsd-update install" + + + Using &os.stable; + + &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;. This is still a + development branch and, at any given time, the sources for + &os.stable; may or may not be suitable for general use. It is + simply another engineering development track, not a resource + for end-users. Users who do not have the resources to perform + testing should instead run the most recent release of + &os;. + + Those interested in tracking or contributing to the &os; + development process, especially as it relates to the next + release of &os;, should consider following &os.stable;. + + While the &os.stable; branch should compile and run at all + times, this cannot be guaranteed. Since more people run + &os.stable; than &os.current;, it is inevitable that bugs and + corner cases will sometimes be found in &os.stable; that were + not apparent in &os.current;. For this reason, one should not + blindly track &os.stable;. It is particularly important + not to update any production servers to + &os.stable; without thoroughly testing the code in a + development or testing environment. + + To track &os.stable;: + + + -STABLE + using + + + + Join the &a.stable.name; list in order to stay + informed of build dependencies that may appear in + &os.stable; or any other issues requiring special + attention. Developers will also make announcements in + this mailing list when they are contemplating some + controversial fix or update, giving the users a chance to + respond if they have any issues to raise concerning the + proposed change. + + Join the relevant svn list + for the branch being tracked. For example, users + tracking the 9-STABLE branch should join the + &a.svn-src-stable-9.name; list. This list records the + commit log entry for each change as it is made, along + with any pertinent information on possible + side effects. + + To join these lists, go to &a.mailman.lists.link;, + click on the list to subscribe to, and follow the + instructions. In order to track changes for the whole + source tree, subscribe to &a.svn-src-all.name;. + + + + To install a new &os.stable; system, install the most + recent &os.stable; release from the &os; mirror sites or use a + monthly snapshot built from &os.stable;. Refer to www.freebsd.org/snapshots + for more information about snapshots. + + To compile or upgrade to an existing &os; system to + &os.stable;, use svn + + Subversion + to check out the source for the desired + branch. Branch names, such as + stable/9, are listed at www.freebsd.org/releng. + + + + Before compiling or upgrading to &os.stable; + + -STABLE + compiling + , read /usr/src/Makefile + carefully and follow the instructions in . Read the &a.stable; and + /usr/src/UPDATING to keep up-to-date + on other bootstrapping procedures that sometimes become + necessary on the road to the next release. + + +