From owner-svn-doc-head@FreeBSD.ORG Tue Feb 4 23:59:19 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 397C7B7B; Tue, 4 Feb 2014 23:59:19 +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 233531BFD; Tue, 4 Feb 2014 23:59:19 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s14NxJSv024741; Tue, 4 Feb 2014 23:59:19 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s14NxJ9d024740; Tue, 4 Feb 2014 23:59:19 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402042359.s14NxJ9d024740@svn.freebsd.org> From: Dru Lavigne Date: Tue, 4 Feb 2014 23:59:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43782 - 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 23:59:19 -0000 Author: dru Date: Tue Feb 4 23:59:18 2014 New Revision: 43782 URL: http://svnweb.freebsd.org/changeset/doc/43782 Log: Whitespace fix only. Translators can ignore. 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 23:35:45 2014 (r43781) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Tue Feb 4 23:59:18 2014 (r43782) @@ -1137,242 +1137,233 @@ before running "/usr/sbin/freebsd-update -CURRENT -STABLE - &os; has two development branches: &os.current; - and &os.stable;. - + &os; has two development branches: &os.current; and + &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. + intended audience as well as how to keep a system up-to-date + with each respective branch. + + + Using &os.current; - - Using &os.current; &os.current; is the bleeding edge of &os; - development and &os.current; users are expected to have a high - degree of technical skill. Less technical users who wish - to track a development branch should - track &os.stable; instead. - - &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. While many - &os; developers compile the &os.current; source code daily, - 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 - new functionality can be a matter of when the - source code was synced. - - &os.current; is made available for three primary - interest groups: - - - - Members of the &os; community who are actively - working on some part of the source tree. - - - - Members of the &os; community who are active - testers. They are willing to spend time solving problems, - making topical suggestions on - changes and the general direction of &os;, and submitting - patches. - - - - 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; 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. &os.current; is not in any way officially - supported. + development and &os.current; users are expected to have a + high degree of technical skill. Less technical users who wish + to track a development branch should track &os.stable; + instead. + + &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. While many &os; developers compile + the &os.current; source code daily, 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 new functionality can be a + matter of when the source code was synced. - - -CURRENT - using - + &os.current; is made available for three primary interest + groups: - To track &os.current;: - - - - Join the &a.current.name; and the - &a.svn-src-head.name; lists. This is - essential in order to see the - comments that people are making about the current state - of the system and to receive important bulletins about - the current state of &os.current;. - - The &a.svn-src-head.name; 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 to the whole - source tree, not just the changes to &os.current;, subscribe to the &a.svn-src-all.name; - list. - - - - 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. - - Users with very slow or limited Internet connectivity - can instead use CTM, but it - is not as reliable as - svn and - svn is the - recommended method for synchronizing - source. - + + + Members of the &os; community who are actively + working on some part of the source tree. + - - 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. + + Members of the &os; community who are active testers. + They are willing to spend time solving problems, making + topical suggestions on changes and the general direction + of &os;, and submitting patches. + - Before compiling - &os.current; - - -CURRENT + + 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; 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. &os.current; is + not in any way officially supported. + + + -CURRENT + using + + + To track &os.current;: + + + + Join the &a.current.name; and the + &a.svn-src-head.name; lists. This is + essential in order to see the + comments that people are making about the current state + of the system and to receive important bulletins about + the current state of &os.current;. + + The &a.svn-src-head.name; 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 to the whole + source tree, not just the changes to &os.current;, + subscribe to the &a.svn-src-all.name; list. + + + + 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. + + Users with very slow or limited Internet connectivity + can instead use CTM, but it is + not as reliable as svn and + svn is the recommended method + for synchronizing source. + + + + 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; + + -CURRENT compiling - , read - /usr/src/Makefile very carefully and follow the instructions in - Rebuilding - "world". Read the &a.current; and - /usr/src/UPDATING to stay - up-to-date on other bootstrapping procedures that - sometimes become necessary on the road to the next - release. - - - - Be active! &os.current; users are encouraged to - submit their suggestions for enhancements or bug fixes. - Suggestions with accompanying code are always - welcome. - - + , read /usr/src/Makefile + very carefully and follow the instructions in + Rebuilding "world". + Read the &a.current; and + /usr/src/UPDATING to stay + up-to-date on other bootstrapping procedures that + sometimes become necessary on the road to the next + release. + + + + Be active! &os.current; users are encouraged to + submit their suggestions for enhancements or bug fixes. + Suggestions with accompanying code are always + welcome. + + 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. + &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 + 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 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 identified in - the release - engineering page. CTM can be used - - -STABLE - syncing with CTM - if a reliable Internet connection is not available. - + + + + 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;. + - - Before compiling or upgrading to &os.stable; + + 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 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 identified in the release + engineering page. CTM can be used + -STABLE + syncing with CTM + if a reliable Internet connection is not + available. + + + + Before compiling or upgrading to &os.stable; + + -STABLE compiling - , read - /usr/src/Makefile carefully and follow the instructions in - Rebuilding - "world". Read &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. - - + , read /usr/src/Makefile + carefully and follow the instructions in Rebuilding "world". Read + &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. + +