Whitespace fix only. Translators can ignore.
Sponsored by: iXsystems
This commit is contained in:
Dru Lavigne
parent
9c9eda4488
commit
5ede7f3b1f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=43782
1 changed files with 193 additions and 202 deletions
|
|
@ -1137,242 +1137,233 @@ before running "/usr/sbin/freebsd-update install"</screen>
|
|||
<indexterm><primary>-CURRENT</primary></indexterm>
|
||||
<indexterm><primary>-STABLE</primary></indexterm>
|
||||
|
||||
<para>&os; has two development branches: &os.current;
|
||||
and &os.stable;.</para>
|
||||
|
||||
<para>&os; has two development branches: &os.current; and
|
||||
&os.stable;.</para>
|
||||
|
||||
<para>This section provides an explanation of each branch and its
|
||||
intended audience as well as
|
||||
how to keep a system up-to-date with each
|
||||
respective branch.</para>
|
||||
intended audience as well as how to keep a system up-to-date
|
||||
with each respective branch.</para>
|
||||
|
||||
<sect2 xml:id="current">
|
||||
<title>Using &os.current;</title>
|
||||
|
||||
<sect2 xml:id="current">
|
||||
<title>Using &os.current;</title>
|
||||
<para>&os.current; is the <quote>bleeding edge</quote> of &os;
|
||||
development and &os.current; users are expected to have a high
|
||||
degree of technical skill. Less technical users who wish
|
||||
to track a development branch should
|
||||
track &os.stable; instead.</para>
|
||||
development and &os.current; users are expected to have a
|
||||
high degree of technical skill. Less technical users who wish
|
||||
to track a development branch should track &os.stable;
|
||||
instead.</para>
|
||||
|
||||
<para>&os.current; is the very latest source code for &os; and
|
||||
includes works in progress, experimental changes, and
|
||||
transitional mechanisms that might or might not be present
|
||||
in the next official release. While many
|
||||
&os; developers compile the &os.current; source code daily,
|
||||
there are short periods of time when the source may not be
|
||||
buildable. These problems are resolved as quickly as
|
||||
possible, but whether or not &os.current; brings disaster or
|
||||
new functionality can be a matter of when the
|
||||
source code was synced.</para>
|
||||
<para>&os.current; is the very latest source code for &os; and
|
||||
includes works in progress, experimental changes, and
|
||||
transitional mechanisms that might or might not be present in
|
||||
the next official release. While many &os; developers compile
|
||||
the &os.current; source code daily, there are short periods of
|
||||
time when the source may not be buildable. These problems are
|
||||
resolved as quickly as possible, but whether or not
|
||||
&os.current; brings disaster or new functionality can be a
|
||||
matter of when the source code was synced.</para>
|
||||
|
||||
<para>&os.current; is made available for three primary
|
||||
interest groups:</para>
|
||||
<para>&os.current; is made available for three primary interest
|
||||
groups:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Members of the &os; community who are actively
|
||||
working on some part of the source tree.</para>
|
||||
</listitem>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Members of the &os; community who are actively
|
||||
working on some part of the source tree.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Members of the &os; community who are active
|
||||
testers. They are willing to spend time solving problems,
|
||||
making topical suggestions on
|
||||
changes and the general direction of &os;, and submitting
|
||||
patches.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Members of the &os; community who are active testers.
|
||||
They are willing to spend time solving problems, making
|
||||
topical suggestions on changes and the general direction
|
||||
of &os;, and submitting patches.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Users who wish to keep an eye on things,
|
||||
use the current source for reference purposes, or
|
||||
make the occasional comment or
|
||||
code contribution.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
<listitem>
|
||||
<para>Users who wish to keep an eye on things, use the
|
||||
current source for reference purposes, or make the
|
||||
occasional comment or code contribution.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>&os.current; should <emphasis>not</emphasis> be
|
||||
considered a fast-track to getting new features before the next
|
||||
release as pre-release features are not yet fully tested
|
||||
and most likely contain bugs. It is not a quick way of getting bug fixes as any given commit
|
||||
is just as likely to introduce new bugs as to fix
|
||||
existing ones. &os.current; is not in any way <quote>officially
|
||||
supported</quote>.</para>
|
||||
<para>&os.current; should <emphasis>not</emphasis> be
|
||||
considered a fast-track to getting new features before the
|
||||
next release as pre-release features are not yet fully tested
|
||||
and most likely contain bugs. It is not a quick way of
|
||||
getting bug fixes as any given commit is just as likely to
|
||||
introduce new bugs as to fix existing ones. &os.current; is
|
||||
not in any way <quote>officially supported</quote>.</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>-CURRENT</primary>
|
||||
<secondary>using</secondary>
|
||||
</indexterm>
|
||||
<indexterm>
|
||||
<primary>-CURRENT</primary>
|
||||
<secondary>using</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>To track &os.current;:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Join the &a.current.name; and the
|
||||
&a.svn-src-head.name; lists. This is
|
||||
<emphasis>essential</emphasis> in order to see the
|
||||
comments that people are making about the current state
|
||||
of the system and to receive important bulletins about
|
||||
the current state of &os.current;.</para>
|
||||
<para>To track &os.current;:</para>
|
||||
|
||||
<para>The &a.svn-src-head.name; list records the commit
|
||||
log entry for each change as it is made, along with any
|
||||
pertinent information on possible side-effects.</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Join the &a.current.name; and the
|
||||
&a.svn-src-head.name; lists. This is
|
||||
<emphasis>essential</emphasis> in order to see the
|
||||
comments that people are making about the current state
|
||||
of the system and to receive important bulletins about
|
||||
the current state of &os.current;.</para>
|
||||
|
||||
<para>To join these lists, go to &a.mailman.lists.link;,
|
||||
click on the list to subscribe to, and follow the
|
||||
instructions. In order to track changes to the whole
|
||||
source tree, not just the changes to &os.current;, subscribe to the &a.svn-src-all.name;
|
||||
list.</para>
|
||||
</listitem>
|
||||
<para>The &a.svn-src-head.name; list records the commit log
|
||||
entry for each change as it is made, along with any
|
||||
pertinent information on possible side-effects.</para>
|
||||
|
||||
<listitem>
|
||||
<para>Synchronize with the &os.current; sources. Typically,
|
||||
<link linkend="svn">svn</link> is used
|
||||
to check out
|
||||
the -CURRENT code from the <literal>head</literal>
|
||||
branch of one of the <link
|
||||
linkend="svn-mirrors">Subversion mirror
|
||||
sites</link>.</para>
|
||||
<para>To join these lists, go to &a.mailman.lists.link;,
|
||||
click on the list to subscribe to, and follow the
|
||||
instructions. In order to track changes to the whole
|
||||
source tree, not just the changes to &os.current;,
|
||||
subscribe to the &a.svn-src-all.name; list.</para>
|
||||
</listitem>
|
||||
|
||||
<para>Users with very slow or limited Internet connectivity
|
||||
can instead use <link linkend="ctm">CTM</link>, but it
|
||||
is not as reliable as
|
||||
<application>svn</application> and
|
||||
<application>svn</application> is the
|
||||
recommended method for synchronizing
|
||||
source.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Synchronize with the &os.current; sources. Typically,
|
||||
<link linkend="svn">svn</link> is used to check out the
|
||||
-CURRENT code from the <literal>head</literal> branch of
|
||||
one of the <link linkend="svn-mirrors">Subversion mirror
|
||||
sites</link>.</para>
|
||||
|
||||
<listitem>
|
||||
<para> Due to the size of the repository, some users choose
|
||||
to only synchronize the sections of source that interest them
|
||||
or which they are contributing patches to.
|
||||
However, users that plan to compile the operating system from
|
||||
source must download <emphasis>all</emphasis> of
|
||||
&os.current;, not just selected portions.</para>
|
||||
<para>Users with very slow or limited Internet connectivity
|
||||
can instead use <link linkend="ctm">CTM</link>, but it is
|
||||
not as reliable as <application>svn</application> and
|
||||
<application>svn</application> is the recommended method
|
||||
for synchronizing source.</para>
|
||||
</listitem>
|
||||
|
||||
<para>Before compiling
|
||||
&os.current;
|
||||
<indexterm>
|
||||
<primary>-CURRENT</primary>
|
||||
<listitem>
|
||||
<para> Due to the size of the repository, some users choose
|
||||
to only synchronize the sections of source that interest
|
||||
them or which they are contributing patches to. However,
|
||||
users that plan to compile the operating system from
|
||||
source must download <emphasis>all</emphasis> of
|
||||
&os.current;, not just selected portions.</para>
|
||||
|
||||
<para>Before compiling &os.current;
|
||||
<indexterm>
|
||||
<primary>-CURRENT</primary>
|
||||
<secondary>compiling</secondary>
|
||||
</indexterm>, read
|
||||
<filename>/usr/src/Makefile</filename> very carefully and follow the instructions in
|
||||
<link linkend="makeworld">Rebuilding
|
||||
"world"</link>. Read the &a.current; and
|
||||
<filename>/usr/src/UPDATING</filename> to stay
|
||||
up-to-date on other bootstrapping procedures that
|
||||
sometimes become necessary on the road to the next
|
||||
release.</para>
|
||||
</listitem>
|
||||
</indexterm>, read <filename>/usr/src/Makefile</filename>
|
||||
very carefully and follow the instructions in
|
||||
<link linkend="makeworld">Rebuilding "world"</link>.
|
||||
Read the &a.current; and
|
||||
<filename>/usr/src/UPDATING</filename> to stay
|
||||
up-to-date on other bootstrapping procedures that
|
||||
sometimes become necessary on the road to the next
|
||||
release.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Be active! &os.current; users are encouraged to
|
||||
submit their suggestions for enhancements or bug fixes.
|
||||
Suggestions with accompanying code are always
|
||||
welcome.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
<listitem>
|
||||
<para>Be active! &os.current; users are encouraged to
|
||||
submit their suggestions for enhancements or bug fixes.
|
||||
Suggestions with accompanying code are always
|
||||
welcome.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</sect2>
|
||||
|
||||
<sect2 xml:id="stable">
|
||||
<title>Using &os.stable;</title>
|
||||
|
||||
<para>&os.stable; is the development branch from which major
|
||||
releases are made. Changes go into this branch at a
|
||||
slower pace and with the general assumption that they
|
||||
have first been tested in &os.current;. This is
|
||||
<emphasis>still</emphasis> a development branch and,
|
||||
at any given time, the sources for
|
||||
&os.stable; may or may not be suitable for general use.
|
||||
It is simply another engineering development
|
||||
track, not a resource for end-users. Users who do not have the resources to perform
|
||||
testing should instead run the most
|
||||
recent release of &os;.</para>
|
||||
<para>&os.stable; is the development branch from which major
|
||||
releases are made. Changes go into this branch at a slower
|
||||
pace and with the general assumption that they have first been
|
||||
tested in &os.current;. This is <emphasis>still</emphasis> a
|
||||
development branch and, at any given time, the sources for
|
||||
&os.stable; may or may not be suitable for general use. It is
|
||||
simply another engineering development track, not a resource
|
||||
for end-users. Users who do not have the resources to perform
|
||||
testing should instead run the most recent release of
|
||||
&os;.</para>
|
||||
|
||||
<para>Those interested in tracking or contributing to the
|
||||
&os; development process, especially as it relates to the
|
||||
next release of &os;, should
|
||||
consider following &os.stable;.</para>
|
||||
<para>Those interested in tracking or contributing to the &os;
|
||||
development process, especially as it relates to the next
|
||||
release of &os;, should consider following &os.stable;.</para>
|
||||
|
||||
<para>While the &os.stable; branch should compile and run at
|
||||
all times, this cannot be guaranteed. Since
|
||||
more people run &os.stable; than &os.current;,
|
||||
it is inevitable that bugs and corner cases will
|
||||
sometimes be found in &os.stable; that were not apparent in
|
||||
&os.current;. For this reason, one should not
|
||||
blindly track &os.stable;. It is particularly important <emphasis>not</emphasis>
|
||||
to update any production servers to &os.stable; without
|
||||
thoroughly testing the code in a development or testing
|
||||
environment.</para>
|
||||
<para>While the &os.stable; branch should compile and run at all
|
||||
times, this cannot be guaranteed. Since more people run
|
||||
&os.stable; than &os.current;, it is inevitable that bugs and
|
||||
corner cases will sometimes be found in &os.stable; that were
|
||||
not apparent in &os.current;. For this reason, one should not
|
||||
blindly track &os.stable;. It is particularly important
|
||||
<emphasis>not</emphasis> to update any production servers to
|
||||
&os.stable; without thoroughly testing the code in a
|
||||
development or testing environment.</para>
|
||||
|
||||
<para>To track &os.stable;:</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>-STABLE</primary>
|
||||
<para>To track &os.stable;:</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>-STABLE</primary>
|
||||
<secondary>using</secondary>
|
||||
</indexterm>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Join the &a.stable.name; list in order to stay
|
||||
informed of build dependencies that may appear in
|
||||
&os.stable; or any other issues requiring special
|
||||
attention. Developers will also make announcements in
|
||||
this mailing list when they are contemplating some
|
||||
controversial fix or update, giving the users a chance
|
||||
to respond if they have any issues to raise concerning
|
||||
the proposed change.</para>
|
||||
</indexterm>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Join the &a.stable.name; list in order to stay
|
||||
informed of build dependencies that may appear in
|
||||
&os.stable; or any other issues requiring special
|
||||
attention. Developers will also make announcements in
|
||||
this mailing list when they are contemplating some
|
||||
controversial fix or update, giving the users a chance to
|
||||
respond if they have any issues to raise concerning the
|
||||
proposed change.</para>
|
||||
|
||||
<para>Join the relevant <application>svn</application>
|
||||
list for the branch being tracked. For example, users
|
||||
tracking the 9-STABLE branch should join the
|
||||
&a.svn-src-stable-9.name; list. This list records the
|
||||
commit log entry for each change as it is made, along
|
||||
with any pertinent information on possible
|
||||
side-effects.</para>
|
||||
<para>Join the relevant <application>svn</application> list
|
||||
for the branch being tracked. For example, users
|
||||
tracking the 9-STABLE branch should join the
|
||||
&a.svn-src-stable-9.name; list. This list records the
|
||||
commit log entry for each change as it is made, along
|
||||
with any pertinent information on possible
|
||||
side-effects.</para>
|
||||
|
||||
<para>To join these lists,
|
||||
go to &a.mailman.lists.link;, click on the list to
|
||||
subscribe to, and follow the instructions. In order to
|
||||
track changes for the whole source tree, subscribe to
|
||||
&a.svn-src-all.name;.</para>
|
||||
</listitem>
|
||||
<para>To join these lists, go to &a.mailman.lists.link;,
|
||||
click on the list to subscribe to, and follow the
|
||||
instructions. In order to track changes for the whole
|
||||
source tree, subscribe to &a.svn-src-all.name;.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>To install a new &os.stable; system, install the most recent &os.stable; release from the
|
||||
<link linkend="mirrors">&os; mirror sites</link> or use a monthly snapshot
|
||||
built from &os.stable;. Refer to <link
|
||||
xlink:href="&url.base;/snapshots/">Snapshots</link>
|
||||
for more information about snapshots.</para>
|
||||
<listitem>
|
||||
<para>To install a new &os.stable; system, install the most
|
||||
recent &os.stable; release from the <link
|
||||
linkend="mirrors">&os; mirror sites</link> or use a
|
||||
monthly snapshot built from &os.stable;. Refer to <link
|
||||
xlink:href="&url.base;/snapshots/">Snapshots</link> for
|
||||
more information about snapshots.</para>
|
||||
|
||||
<para>To compile or upgrade to an existing &os;
|
||||
system to &os.stable;, use <link linkend="svn">svn</link>
|
||||
<indexterm>
|
||||
<primary>Subversion</primary>
|
||||
</indexterm> to check out the source for the desired
|
||||
branch.
|
||||
Branch names, such as <literal>stable/9</literal>, are identified in
|
||||
<link xlink:href="&url.base;/releng/">the release
|
||||
engineering page</link>. <link linkend="ctm">CTM</link> can be used
|
||||
<indexterm>
|
||||
<primary>-STABLE</primary>
|
||||
<secondary>syncing with CTM</secondary>
|
||||
</indexterm> if a reliable Internet connection is not available.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Before compiling or upgrading to &os.stable;<indexterm>
|
||||
<para>To compile or upgrade to an existing &os; system to
|
||||
&os.stable;, use <link linkend="svn">svn</link>
|
||||
<indexterm>
|
||||
<primary>Subversion</primary>
|
||||
</indexterm> to check out the source for the desired
|
||||
branch. Branch names, such as
|
||||
<literal>stable/9</literal>, are identified in <link
|
||||
xlink:href="&url.base;/releng/">the release
|
||||
engineering page</link>. <link
|
||||
linkend="ctm">CTM</link> can be used
|
||||
<indexterm>
|
||||
<primary>-STABLE</primary>
|
||||
<secondary>syncing with CTM</secondary>
|
||||
</indexterm> if a reliable Internet connection is not
|
||||
available.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Before compiling or upgrading to &os.stable;
|
||||
<indexterm>
|
||||
<primary>-STABLE</primary>
|
||||
<secondary>compiling</secondary>
|
||||
</indexterm>, read
|
||||
<filename>/usr/src/Makefile</filename> carefully and follow the instructions in
|
||||
<link linkend="makeworld">Rebuilding
|
||||
"world"</link>. Read &a.stable; and
|
||||
<filename>/usr/src/UPDATING</filename> to keep
|
||||
up-to-date on other bootstrapping procedures that
|
||||
sometimes become necessary on the road to the next
|
||||
release.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</indexterm>, read <filename>/usr/src/Makefile</filename>
|
||||
carefully and follow the instructions in <link
|
||||
linkend="makeworld">Rebuilding "world"</link>. Read
|
||||
&a.stable; and <filename>/usr/src/UPDATING</filename> to
|
||||
keep up-to-date on other bootstrapping procedures that
|
||||
sometimes become necessary on the road to the next
|
||||
release.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue