svn commit: r53606 - head/en_US.ISO8859-1/books/faq
Mark Linimon
linimon at FreeBSD.org
Wed Nov 20 05:21:21 UTC 2019
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.</para>
- <para>&os; <link
- xlink:href="&url.base;/snapshots/">snapshot</link>
- releases are made based on the current state of the
- <emphasis>-CURRENT</emphasis> and
- <emphasis>-STABLE</emphasis> branches. The goals behind
- each snapshot release are:</para>
-
- <itemizedlist>
- <listitem>
- <para>To test the latest version of the installation
- software.</para>
- </listitem>
-
- <listitem>
- <para>To give people who would like to run
- <emphasis>-CURRENT</emphasis> or
- <emphasis>-STABLE</emphasis> 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.</para>
- </listitem>
-
- <listitem>
- <para>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.)</para>
- </listitem>
-
- <listitem>
- <para>To ensure that all new features and fixes in need
- of testing have the greatest possible number of
- potential testers.</para>
- </listitem>
- </itemizedlist>
-
- <para>No claims are made that any
- <emphasis>-CURRENT</emphasis> snapshot can be considered
- <quote>production quality</quote> for any purpose.
- If a stable and fully tested system is needed,
- stick to full releases.</para>
-
- <para>Snapshot releases are directly available from <link
- xlink:href="&url.base;/snapshots/">snapshot</link>.</para>
-
- <para>Official snapshots are generated on a regular
- basis for all actively developed branches.</para>
</answer>
</qandaentry>
@@ -504,6 +457,62 @@
<para>For people who need or want a little more excitement,
binary snapshots are made weekly as discussed
above.</para>
+ </answer>
+ </qandaentry>
+
+ <qandaentry>
+ <question xml:id="snapshot-freq">
+ <para>When are &os; snapshots made?</para>
+ </question>
+
+ <answer>
+ <para>&os; <link
+ xlink:href="&url.base;/snapshots/">snapshot</link>
+ releases are made based on the current state of the
+ <emphasis>-CURRENT</emphasis> and
+ <emphasis>-STABLE</emphasis> branches. The goals behind
+ each snapshot release are:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>To test the latest version of the installation
+ software.</para>
+ </listitem>
+
+ <listitem>
+ <para>To give people who would like to run
+ <emphasis>-CURRENT</emphasis> or
+ <emphasis>-STABLE</emphasis> 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.</para>
+ </listitem>
+
+ <listitem>
+ <para>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.)</para>
+ </listitem>
+
+ <listitem>
+ <para>To ensure that all new features and fixes in need
+ of testing have the greatest possible number of
+ potential testers.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>No claims are made that any
+ <emphasis>-CURRENT</emphasis> snapshot can be considered
+ <quote>production quality</quote> for any purpose.
+ If a stable and fully tested system is needed,
+ stick to full releases.</para>
+
+ <para>Snapshot releases are directly available from <link
+ xlink:href="&url.base;/snapshots/">snapshot</link>.</para>
+
+ <para>Official snapshots are generated on a regular
+ basis for all actively developed branches.</para>
</answer>
</qandaentry>
More information about the svn-doc-all
mailing list