From owner-svn-doc-head@FreeBSD.ORG Tue Feb 4 22:40:49 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B84B5D39; Tue, 4 Feb 2014 22:40:49 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9617115E1; Tue, 4 Feb 2014 22:40:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s14Mensp095135; Tue, 4 Feb 2014 22:40:49 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s14MendE095134; Tue, 4 Feb 2014 22:40:49 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402042240.s14MendE095134@svn.freebsd.org> From: Dru Lavigne Date: Tue, 4 Feb 2014 22:40:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43780 - head/en_US.ISO8859-1/books/handbook/cutting-edge 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.17 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: Tue, 04 Feb 2014 22:40:49 -0000 Author: dru Date: Tue Feb 4 22:40:49 2014 New Revision: 43780 URL: http://svnweb.freebsd.org/changeset/doc/43780 Log: Improve flow and clarity of first 1/2 of this section. 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 Tue Feb 4 21:57:41 2014 (r43779) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Tue Feb 4 22:40:49 2014 (r43780) @@ -1140,28 +1140,28 @@ before running "/usr/sbin/freebsd-update &os; has two development branches: &os.current; and &os.stable;. - This section provides an explanation of each - and describes how to keep a system up-to-date with each - respective branch. &os.current; will be discussed first, then - &os.stable;. + This section provides an explanation of each branch and its + intended audience as well as + how to keep a system up-to-date with each + respective branch. Using &os.current; &os.current; is the bleeding edge of &os; - development. &os.current; users are expected to have a high - degree of technical skill and should be capable of solving - difficult system problems on their own. If you are new to - &os;, track &os.stable; instead. + development and &os.current; users are expected to have a high + degree of technical skill. Less technical users who wish + to track a development brach should + track &os.stable; instead. - &os.current; is the very latest source code for &os;. - This includes work in progress, experimental changes, and + &os.current; is the very latest source code for &os; and + includes works in progress, experimental changes, and transitional mechanisms that might or might not be present - in the next official release of the software. While many + in the next official release. While many &os; developers compile the &os.current; source code daily, - there are periods of time when the sources are not + there are short periods of time when the source may not be buildable. These problems are resolved as quickly as possible, but whether or not &os.current; brings disaster or - greatly desired functionality can be a matter of when the + new functionality can be a matter of when the source code was synced. &os.current; is made available for three primary @@ -1170,53 +1170,40 @@ before running "/usr/sbin/freebsd-update Members of the &os; community who are actively - working on some part of the source tree and for whom - keeping current is an absolute - requirement. + working on some part of the source tree. Members of the &os; community who are active - testers, willing to spend time solving problems in order - to ensure that &os.current; remains as sane as possible. - These testers wish to make topical suggestions on - changes and the general direction of &os;, and submit - patches to implement them. + testers. They are willing to spend time solving problems, + making topical suggestions on + changes and the general direction of &os;, and submitting + patches. - Those who merely wish to keep an eye on things, or - to use the current sources for reference purposes. - These people also make the occasional comment or - contribute code. + Users who wish to keep an eye on things, + use the current source for reference purposes, or + make the occasional comment or + code contribution. - &os.current; is Not: - - - - A fast-track to getting new features before the next - release. Pre-release features are not yet fully tested - and most likely contain bugs. - - - - A quick way of getting bug fixes. Any given commit + &os.current; should not be + considered a fast-track to getting new features before the next + release as pre-release features are not yet fully tested + and most likely contain bugs. It is not a quick way of getting bug fixes as any given commit is just as likely to introduce new bugs as to fix - existing ones. - - - - In any way officially + existing ones. &os.current; is not in any way officially supported. - - -CURRENT using + + To track &os.current;: + Join the &a.current.name; and the @@ -1238,57 +1225,30 @@ before running "/usr/sbin/freebsd-update - Grab the sources from a &os; - mirror site using - one of the following methods: - - - - Use svn - - Subversion - - - -CURRENT - Syncing with - Subversion - - to check out the desired development or release - branch. This is the recommended method, providing - access to &os; development as it occurs. Checkout + Synchronize with the &os.current; sources. Typically, + svn is used + to check out the -CURRENT code from the head branch of one of the Subversion mirror - sites. Due to the size of the repository, - it is recommended that only desired subtrees be - checked out. - + sites. - - Use the - CTM - - -CURRENT - Syncing with CTM - facility. If you have bad connectivity - such as high price connections or only email access, - CTM is an option, but it + Users with very slow or limited Internet connectivity + can instead use CTM, but it is not as reliable as - Subversion. For this - reason, Subversion is the - recommended method for any system with Internet - connectivity. + svn and + svn is the + recommended method for synchronizing + source. - - - If you plan to run, and not just look at the - sources, download all of - &os.current;, not just selected portions. Various parts - of the source depend on updates elsewhere, and trying to - compile just a subset is almost guaranteed to cause - problems. + Due to the size of the repository, some users choose + to only synchronize the sections of source that interest them + or which they are contributing patches to. + However, users that plan to compile the operating system from + source must download all of + &os.current;, not just selected portions. Before compiling &os.current; @@ -1309,8 +1269,8 @@ before running "/usr/sbin/freebsd-update Be active! &os.current; users are encouraged to submit their suggestions for enhancements or bug fixes. - Suggestions with accompanying code are received most - enthusiastically! + Suggestions with accompanying code are always + welcome.