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

Explain the significance of -RC and -BETA.

Browse source 
PR:		 docs/22627
Submitted by:	 Dima Dorfman <dima@unixfreak.org>
This commit is contained in:
Nik Clayton 2000-11-12 16:22:40 +00:00
parent 4f7735ab94
commit 90a28f70a9
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=8347
2 changed files with 68 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

35
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.121 2000/11/09 16:43:18 phantom Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.122 2000/11/09 16:46:13 phantom Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -6526,6 +6526,39 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
</answer>
</qandaentry>
<qandaentry>
<question id="release-candidate">
<para>I tried to update by system to the latest -STABLE, but
got -RC or -BETA! What's going on?</para>
</question>
<answer>
<para>Short answer: it's just a name. RC stands for
<quote>Release Candidate</quote>. It signifies that a
release is imminent. In FreeBSD, -BETA is synonymous with
-RC.</para>
<para>Long answer: FreeBSD derives its releases from one of
two places. Major, dot-zero, releases, such as
3.0-RELEASE and 4.0-RELEASE, are branched from the head of
the development stream, commonly referred to as <link
linkend="current">-CURRENT</link>. Minor releases, such
as 3.1-RELEASE or 4.2-RELEASE, are snapshots of the active
<link linkend="stable">-STABLE</link> branch.</para>
<para>When a release is about to be made, the branch from
which it will be derived from has to undergo a certain
process. Part of this process is a code freeze. When a
code freeze is initiated, the name of the branch is
changed to reflect that it's about to become a release.
For example, if the branch used to be called 4.0-STABLE,
its name will be changed to 4.1-RC to signify that a
release is about to be made from it. Once the release,
4.1-RELEASE in this example, has been made, the branch
will be renamed to 4.1-STABLE.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>

35
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.121 2000/11/09 16:43:18 phantom Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.122 2000/11/09 16:46:13 phantom Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -6526,6 +6526,39 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
</answer>
</qandaentry>
<qandaentry>
<question id="release-candidate">
<para>I tried to update by system to the latest -STABLE, but
got -RC or -BETA! What's going on?</para>
</question>
<answer>
<para>Short answer: it's just a name. RC stands for
<quote>Release Candidate</quote>. It signifies that a
release is imminent. In FreeBSD, -BETA is synonymous with
-RC.</para>
<para>Long answer: FreeBSD derives its releases from one of
two places. Major, dot-zero, releases, such as
3.0-RELEASE and 4.0-RELEASE, are branched from the head of
the development stream, commonly referred to as <link
linkend="current">-CURRENT</link>. Minor releases, such
as 3.1-RELEASE or 4.2-RELEASE, are snapshots of the active
<link linkend="stable">-STABLE</link> branch.</para>
<para>When a release is about to be made, the branch from
which it will be derived from has to undergo a certain
process. Part of this process is a code freeze. When a
code freeze is initiated, the name of the branch is
changed to reflect that it's about to become a release.
For example, if the branch used to be called 4.0-STABLE,
its name will be changed to 4.1-RC to signify that a
release is about to be made from it. Once the release,
4.1-RELEASE in this example, has been made, the branch
will be renamed to 4.1-STABLE.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>