docs/115000: [PATCH] nits and updates to FAQs (part 1)
Ben Kaduk
minimarmot at gmail.com
Sun Jul 29 02:40:02 UTC 2007
>Number: 115000
>Category: docs
>Synopsis: [PATCH] nits and updates to FAQs (part 1)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jul 29 02:40:01 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator: Ben Kaduk
>Release: 7.0-CURRENT
>Organization:
>Environment:
the world-wide web.
>Description:
itemized (but not enumerated) changelist:
o monthly, not daily, snapshots are made available at freebsd.org/snapshots/
o all monthly snapshots (not just the occasional one) are made available
o the paren of the smiley doesn't close the parenthetical expression. do so
o we're heading towards 6.3 now, not 6.2
o eight months between 5.5 and 6.2 (june 2006 to january 2007 -- see newvers.sh commit log)
o the linked snapshots are monthly, not daily
o query-pr-summary and query-pr are functionally equivalent now; linking to query-pr is semantically closer to the active text of the link (and I think -summary is deprecated?)
I am not sure why this text refers to daily snapshots. Perhaps the author was thinking of the tinderboxen? If so, I didn't think their releases were made available, and they certainly aren't on the page that the FAQ links to.
>How-To-Repeat:
>Fix:
Patch attached with submission follows:
--- book.sgml.orig 2007-07-23 20:26:10.000000000 -0500
+++ book.sgml 2007-07-28 21:29:54.000000000 -0500
@@ -367,11 +367,11 @@
groups</quote> on the -CURRENT mailing list may be
treated with contempt.</para>
- <para>Every day, <ulink
+ <para>Every month, <ulink
url="&url.base;/snapshots/">snapshot
</ulink> 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:</para>
<itemizedlist>
@@ -391,7 +391,7 @@
<para>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 :)</para>
+ like this happening :) )</para>
</listitem>
<listitem>
@@ -432,7 +432,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 <quote><ulink url="&url.articles.releng;/release-proc.html#REL-BRANCH">
@@ -467,7 +467,7 @@
<answer>
<para>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 +532,7 @@
<listitem>
<para><ulink
url="&url.base;/snapshots/">
- Snapshot</ulink> releases are made daily for the
+ Snapshot</ulink> releases are made monthly for the
<link linkend="current">-CURRENT</link> and <link
linkend="stable">-STABLE</link> branch, these being
of service purely to bleeding-edge testers and
@@ -561,7 +561,7 @@
<para>The Problem Report database of all user change requests
may be queried by using our web-based PR
<ulink
- url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">
+ url="http://www.FreeBSD.org/cgi/query-pr.cgi?query">
query</ulink>
interface.</para>
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-doc
mailing list