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

Fix misconceptions with BETA and RC.

Browse source
This commit is contained in:
David E. O'Brien 2001-03-08 10:55:14 +00:00
parent 90bca97c56
commit 0d86d09533
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=8916
2 changed files with 24 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.147 2001/02/28 22:47:51 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.148 2001/03/07 20:00:49 hrs Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -6744,8 +6744,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<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>
release is imminent. In FreeBSD, -BETA is typically synonymous
with the code freeze before a release.</para>
<para>Long answer: FreeBSD derives its releases from one of
two places. Major, dot-zero, releases, such as
@ -6761,10 +6761,15 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
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>
its name will be changed to 4.1-BETA to signify the code
freeze and signify that extra pre-release testing should
be happening. Bug fixes can still be committed to be part
of the release. When the source code is in shape for the
release the name will be chagned to 4.1-RC to signify that a
release is about to be made from it. Once in the RC stage,
only the most critical bugs found can be fixed.
Once the release, 4.1-RELEASE in this example, has been made,
the branch will be renamed to 4.1-STABLE.</para>
</answer>
</qandaentry>

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

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.147 2001/02/28 22:47:51 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.148 2001/03/07 20:00:49 hrs Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -6744,8 +6744,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<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>
release is imminent. In FreeBSD, -BETA is typically synonymous
with the code freeze before a release.</para>
<para>Long answer: FreeBSD derives its releases from one of
two places. Major, dot-zero, releases, such as
@ -6761,10 +6761,15 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
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>
its name will be changed to 4.1-BETA to signify the code
freeze and signify that extra pre-release testing should
be happening. Bug fixes can still be committed to be part
of the release. When the source code is in shape for the
release the name will be chagned to 4.1-RC to signify that a
release is about to be made from it. Once in the RC stage,
only the most critical bugs found can be fixed.
Once the release, 4.1-RELEASE in this example, has been made,
the branch will be renamed to 4.1-STABLE.</para>
</answer>
</qandaentry>