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

Whitespace cleanup from last commit.

Browse source 
No content changes.
This commit is contained in:
Michael Lucas 2002-03-21 18:18:41 +00:00
parent 604895c7a5
commit 086333002a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12546
1 changed files with 37 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

75
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -91,29 +91,26 @@
<title>Staying Current with &os;</title>
<para>As you read this, keep in mind that &os.current; is the
<quote>bleeding edge</quote> of &os; development.
&os.current; users are expected
to have a high degree of technical skill, and should be capable
of solving difficult system problems on their own.
If you
are new to &os;, think
<quote>bleeding edge</quote> of &os; development.
&os.current; users are expected to have a high degree of
technical skill, and should be capable of solving difficult
system problems on their own. If you are new to &os;, think
twice before installing it. </para>
<sect3>
<title>What Is &os.current;?</title>
<indexterm><primary>snapshot</primary></indexterm>
<para>&os.current; is the
latest working sources for &os;. This
includes work in progress, experimental changes, and transitional
mechanisms that might or might not be present in the next official
release of the software. While many &os; developers compile
the &os.current; source code daily, there are periods of time when the
sources are not buildable. These problems are
resolved as expeditiously as possible, but whether or
not &os.current; brings disaster or greatly desired
functionality can be a matter of which exact moment
you grabbed the source code in!</para>
<para>&os.current; is the latest working sources for &os;.
This includes work in progress, experimental changes, and
transitional mechanisms that might or might not be present
in the next official release of the software. While many
&os; developers compile the &os.current; source code daily,
there are periods of time when the sources are not
buildable. These problems are resolved as expeditiously as
possible, but whether or not &os.current; brings disaster or
greatly desired functionality can be a matter of which exact
moment you grabbed the source code in!</para>
</sect3>
<sect3>
@ -124,26 +121,27 @@
<orderedlist>
<listitem>
<para>Members of the &os; group who are actively working on
some part of the source tree and for whom keeping
<quote>current</quote> is an absolute requirement.</para>
<para>Members of the &os; group who are actively working
on some part of the source tree and for whom keeping
<quote>current</quote> is an absolute
requirement.</para>
</listitem>
<listitem>
<para>Members of the &os; group who are active testers,
willing to spend time solving problems in order to
ensure that &os.current; remains as sane as possible.
These are also people who wish to make topical suggestions
on changes and the general direction of &os;, and submit
patches to implement them.</para>
These are also people who wish to make topical
suggestions on changes and the general direction of
&os;, and submit patches to implement them.</para>
</listitem>
<listitem>
<para>Those
who merely wish to keep an eye on things, or to use the current
sources for reference purposes (e.g. for
<emphasis>reading</emphasis>, not running). These people
also make the occasional comment or contribute code.</para>
<para>Those who merely wish to keep an eye on things, or
to use the current sources for reference purposes
(e.g. for <emphasis>reading</emphasis>, not running).
These people also make the occasional comment or
contribute code.</para>
</listitem>
</orderedlist>
</sect3>
@ -154,10 +152,11 @@
<orderedlist>
<listitem>
<para>A fast-track to getting pre-release bits because you
heard there is some cool new feature in there and you want
to be the first on your block to have it. Being the first
on the block to get the new feature means that you're the
first on the block to get the new bugs.</para>
heard there is some cool new feature in there and you
want to be the first on your block to have it. Being
the first on the block to get the new feature means that
you're the first on the block to get the new
bugs.</para>
</listitem>
<listitem>
@ -167,13 +166,13 @@
</listitem>
<listitem>
<para>In any way <quote>officially supported</quote>.
We do our best to help people genuinely in one of the 3
<para>In any way <quote>officially supported</quote>. We
do our best to help people genuinely in one of the 3
<quote>legitimate</quote> &os.current; groups, but we
simply <emphasis>do not have the time</emphasis> to provide
tech support. This is not because we are mean and
nasty people who do not like helping people out (we would
not even be doing &os; if we were). We simply
simply <emphasis>do not have the time</emphasis> to
provide tech support. This is not because we are mean
and nasty people who do not like helping people out (we
would not even be doing &os; if we were). We simply
cannot answer hundreds messages a day
<emphasis>and</emphasis> work on FreeBSD! Given the
choice between improving &os; and answering lots of