aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNik Clayton <nik@FreeBSD.org>2000-11-12 16:22:40 +0000
committerNik Clayton <nik@FreeBSD.org>2000-11-12 16:22:40 +0000
commit90a28f70a9b5b4a10c5819f0fa49085ea4fdf6ba (patch)
tree614e0b841c0666c2e32f932a85b1acc0e92f5354
parent4f7735ab946a26b06b2856b03df8ee889c56f8af (diff)
downloaddoc-90a28f70a9b5b4a10c5819f0fa49085ea4fdf6ba.tar.gz
doc-90a28f70a9b5b4a10c5819f0fa49085ea4fdf6ba.zip
Explain the significance of -RC and -BETA.
PR: docs/22627 Submitted by: Dima Dorfman <dima@unixfreak.org>
Notes
Notes: svn path=/head/; revision=8347
-rw-r--r--en_US.ISO8859-1/books/faq/book.sgml35
-rw-r--r--en_US.ISO_8859-1/books/faq/book.sgml35
2 files changed, 68 insertions, 2 deletions
diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index 4687e3baea..b34bc02118 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -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>
diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml
index 4687e3baea..b34bc02118 100644
--- a/en_US.ISO_8859-1/books/faq/book.sgml
+++ b/en_US.ISO_8859-1/books/faq/book.sgml
@@ -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>