From owner-freebsd-doc@FreeBSD.ORG Sat Sep 22 17:40:07 2007 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 219BC16A418 for ; Sat, 22 Sep 2007 17:40:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 06B8013C4BA for ; Sat, 22 Sep 2007 17:40:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l8MHe6oo007876 for ; Sat, 22 Sep 2007 17:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l8MHe6m5007875; Sat, 22 Sep 2007 17:40:06 GMT (envelope-from gnats) Date: Sat, 22 Sep 2007 17:40:06 GMT Message-Id: <200709221740.l8MHe6m5007875@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Ben Kaduk" Cc: Subject: Re: docs/115000: [PATCH] nits and updates to FAQs (part 1) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ben Kaduk List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Sep 2007 17:40:07 -0000 The following reply was made to PR docs/115000; it has been noted by GNATS. From: "Ben Kaduk" To: bug-followup@freebsd.org Cc: Subject: Re: docs/115000: [PATCH] nits and updates to FAQs (part 1) Date: Sat, 22 Sep 2007 13:33:49 -0400 An updated diff is inlined below, but I think gmail may mangle the whitespace, so a text file is also available at http://web.mit.edu/kaduk/www/freebsd/patches/faq/book.sgml.diff.0.txt -Ben Kaduk --------- begin inline patch ------------ --- book.sgml.orig 2007-07-23 21:26:10.000000000 -0400 +++ book.sgml 2007-09-22 13:29:06.000000000 -0400 @@ -367,11 +367,11 @@ groups on the -CURRENT mailing list may be treated with contempt. - Every day, Every month, snapshot releases are made based on the current state of the - -CURRENT and -STABLE branches. Distributions of the - occasional snapshot are made available. The goals + -CURRENT and -STABLE branches. + The goals behind each snapshot release are: @@ -391,7 +391,7 @@ To preserve a fixed reference point for the code in question, just in case we break something really badly later. (Although CVS normally prevents anything horrible - like this happening :) + like this happening :) ) @@ -410,8 +410,11 @@ Snapshot releases are directly available from snapshot. - Snapshots are generated, on the average, daily for - all actively developed branches. + Official snapshots are generated, on the average, monthly for + all actively developed branches. There are also + daily snapshot builds of the popular &arch.i386; + and &arch.amd64 branches, hosted on + snapshots.us.freebsd.org. @@ -432,7 +435,7 @@ only well-tested bug fixes and other small incremental enhancements. FreeBSD-CURRENT, on the other hand, has been one unbroken line since 2.0 was released, leading - towards 6.2-RELEASE and beyond. Just before 6.0-RELEASE, the + towards 6.3-RELEASE and beyond. Just before 6.0-RELEASE, the 6-STABLE branch was created, and &os.current; became 7-CURRENT. For more detailed information, see @@ -467,7 +470,7 @@ The &a.re; releases a new version of FreeBSD about every - four months, on average. Release dates are announced well in + eight months, on average. Release dates are announced well in advance, so that the people working on the system know when their projects need to be finished and tested. A testing period precedes each release, in order to ensure @@ -532,7 +535,7 @@ - Snapshot releases are made daily for the + Snapshot releases are made monthly for the -CURRENT and -STABLE branch, these being of service purely to bleeding-edge testers and @@ -561,7 +564,7 @@ The Problem Report database of all user change requests may be queried by using our web-based PR + url="http://www.FreeBSD.org/cgi/query-pr.cgi?query"> query interface.