From owner-svn-doc-all@freebsd.org Wed Nov 20 05:21:21 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 577071A8951; Wed, 20 Nov 2019 05:21:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47HrdY1h7Lz4LTM; Wed, 20 Nov 2019 05:21:21 +0000 (UTC) (envelope-from linimon@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 1D2E01DEE7; Wed, 20 Nov 2019 05:21:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id xAK5LKKx083001; Wed, 20 Nov 2019 05:21:21 GMT (envelope-from linimon@FreeBSD.org) Received: (from linimon@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id xAK5LK7u083000; Wed, 20 Nov 2019 05:21:20 GMT (envelope-from linimon@FreeBSD.org) Message-Id: <201911200521.xAK5LK7u083000@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: linimon set sender to linimon@FreeBSD.org using -f From: Mark Linimon Date: Wed, 20 Nov 2019 05:21:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53606 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head X-SVN-Commit-Author: linimon X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/faq X-SVN-Commit-Revision: 53606 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.29 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: Wed, 20 Nov 2019 05:21:21 -0000 Author: linimon Date: Wed Nov 20 05:21:20 2019 New Revision: 53606 URL: https://svnweb.freebsd.org/changeset/doc/53606 Log: Move the information about Snapshots out of the "current" Question and into its own Question. No text change. IMHO it flows better this way. 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 Wed Nov 20 05:07:46 2019 (r53605) +++ head/en_US.ISO8859-1/books/faq/book.xml Wed Nov 20 05:21:20 2019 (r53606) @@ -383,53 +383,6 @@ that use &os.current; are expected to be able to analyze, debug, and report problems. - &os; snapshot - releases are made based on the current state of the - -CURRENT and - -STABLE branches. The goals behind - each snapshot release are: - - - - To test the latest version of the installation - software. - - - - To give people who would like to run - -CURRENT or - -STABLE but who do not have the - time or bandwidth to follow it on a day-to-day basis - an easy way of bootstrapping it onto their - systems. - - - - To preserve a fixed reference point for the code - in question, just in case we break something really - badly later. (Although Subversion normally prevents - anything horrible like this happening.) - - - - To ensure that all new features and fixes in need - of testing have the greatest possible number of - potential testers. - - - - No claims are made that any - -CURRENT snapshot can be considered - production quality for any purpose. - If a stable and fully tested system is needed, - stick to full releases. - - Snapshot releases are directly available from snapshot. - - Official snapshots are generated on a regular - basis for all actively developed branches. @@ -504,6 +457,62 @@ For people who need or want a little more excitement, binary snapshots are made weekly as discussed above. + + + + + + When are &os; snapshots made? + + + + &os; snapshot + releases are made based on the current state of the + -CURRENT and + -STABLE branches. The goals behind + each snapshot release are: + + + + To test the latest version of the installation + software. + + + + To give people who would like to run + -CURRENT or + -STABLE but who do not have the + time or bandwidth to follow it on a day-to-day basis + an easy way of bootstrapping it onto their + systems. + + + + To preserve a fixed reference point for the code + in question, just in case we break something really + badly later. (Although Subversion normally prevents + anything horrible like this happening.) + + + + To ensure that all new features and fixes in need + of testing have the greatest possible number of + potential testers. + + + + No claims are made that any + -CURRENT snapshot can be considered + production quality for any purpose. + If a stable and fully tested system is needed, + stick to full releases. + + Snapshot releases are directly available from snapshot. + + Official snapshots are generated on a regular + basis for all actively developed branches.