svn commit: r50157 - head/en_US.ISO8859-1/articles/freebsd-releng
Glen Barber
gjb at FreeBSD.org
Thu Apr 13 16:19:00 UTC 2017
Author: gjb
Date: Thu Apr 13 16:18:59 2017
New Revision: 50157
URL: https://svnweb.freebsd.org/changeset/doc/50157
Log:
Use <literal> tags around 'RC' references as opposed to the
<acronym> tag, which renders differently. Given how some of
this article is written, there are visible differences in the
rendered output that may seem confusing.
Sponsored by: The FreeBSD Foundation
Modified:
head/en_US.ISO8859-1/articles/freebsd-releng/article.xml
head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml
head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml
Modified: head/en_US.ISO8859-1/articles/freebsd-releng/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Wed Apr 12 10:09:36 2017 (r50156)
+++ head/en_US.ISO8859-1/articles/freebsd-releng/article.xml Thu Apr 13 16:18:59 2017 (r50157)
@@ -283,7 +283,7 @@
<listitem>
<para>The Ports quarterly branch used is determined by when
- the final <acronym>RC</acronym> build is planned. A new
+ the final <literal>RC</literal> build is planned. A new
quarterly branch is created on the first day of the quarter,
so this metric should be used when taking the release cycle
milestones into account. The quarterly branch is created by
@@ -298,7 +298,7 @@
<listitem>
<para>The final Ports package build is done by the
&team.portmgr; after the final (or what is expected to be
- final) <acronym>RC</acronym> build.</para>
+ final) <literal>RC</literal> build.</para>
</listitem>
</orderedlist>
@@ -315,7 +315,7 @@
where the target date depends on predefined milestones upon
which there is a dependency. For example, the Ports Collection
release tag originates from the active quarterly branch at the
- time of the last <acronym>RC</acronym>. This in part defines
+ time of the last <literal>RC</literal>. This in part defines
which quarterly branch is used, when the release tag can happen,
and what revision of the ports tree is used for the final
<literal>RELEASE</literal> build.</para>
@@ -334,7 +334,7 @@
approvals, the length of time for the blanket approval should
be made clear. For example, a &os; developer may request
blanket approvals from the start of the code slush until the
- start of the <acronym>RC</acronym> builds.</para>
+ start of the <literal>RC</literal> builds.</para>
<note>
<para>In order to keep track of blanket approvals, the &team.re;
Modified: head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Wed Apr 12 10:09:36 2017 (r50156)
+++ head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Thu Apr 13 16:18:59 2017 (r50157)
@@ -159,7 +159,7 @@ KERNEL="GENERIC64"</programlisting>
or <filename
class="directory">/releng/scripts-release/scripts</filename>
respectfully, to avoid collisions between an
- <acronym>RC</acronym> build from a releng branch versus
+ <literal>RC</literal> build from a releng branch versus
a <literal>STABLE</literal> snapshot from the respective stable
branch.</para>
@@ -205,7 +205,7 @@ KERNEL="GENERIC64"</programlisting>
<para>Similar to building &os; development snapshots,
<filename>thermite.sh</filename> would be invoked the same way.
The difference between development snapshots and release builds,
- <literal>BETA</literal> and <acronym>RC</acronym>, included, is
+ <literal>BETA</literal> and <literal>RC</literal>, included, is
that the &man.chroot.8; configuration files must be named with
<literal>release</literal> instead of <literal>snap</literal> as
the "type", as mentioned above.</para>
@@ -219,7 +219,7 @@ KERNEL="GENERIC64"</programlisting>
respectively.</para>
<para>When building <literal>BETA</literal>,
- <acronym>RC</acronym>, and the final <literal>RELEASE</literal>,
+ <literal>RC</literal>, and the final <literal>RELEASE</literal>,
also statically set <literal>BUILDSVNREV</literal> to the
revision on the branch reflecting the name change,
<literal>BUILDDATE</literal> to the date the builds are started
Modified: head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml Wed Apr 12 10:09:36 2017 (r50156)
+++ head/en_US.ISO8859-1/articles/freebsd-releng/releng-minor-version.xml Thu Apr 13 16:18:59 2017 (r50157)
@@ -89,7 +89,7 @@
<sect2 xml:id="releng-stable-branching">
<title>Creating the &branch.relengx; Branch</title>
- <para>When the first <acronym>RC</acronym> (Release Candidate)
+ <para>When the first <literal>RC</literal> (Release Candidate)
build is ready to begin, the &branch.releng; branch is created.
This is a multi-step process that must be done in a specific
order, in order to avoid anomalies such as overlaps with
@@ -165,7 +165,7 @@
<filename>head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml</filename>
in the Documentation Project repository.</para>
- <para>After the first <acronym>RC</acronym> build has completed
+ <para>After the first <literal>RC</literal> build has completed
and tested, the &branch.stable; branch can be
<quote>thawed</quote> by removing (or commenting) the
^/&branch.stablex; entry in
More information about the svn-doc-all
mailing list