os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Move the information about Snapshots out of the "current" Question and

Browse source 
into its own Question.  No text change.  IMHO it flows better this way.
This commit is contained in:
Mark Linimon 2019-11-20 05:21:20 +00:00
parent 6c3c6ea31c
commit 31f9ae090b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=53606
1 changed files with 56 additions and 47 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

103
en_US.ISO8859-1/books/faq/book.xml
View file

@ -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>
@ -507,6 +460,62 @@
</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>
<qandaentry>
<question xml:id="responsible">
<para>Who is responsible for &os;?</para>