Date: Tue, 7 Feb 2017 19:29:31 +0000 (UTC) From: Glen Barber <gjb@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-user@freebsd.org Subject: svn commit: r49948 - user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng Message-ID: <201702071929.v17JTVhq030815@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: gjb Date: Tue Feb 7 19:29:31 2017 New Revision: 49948 URL: https://svnweb.freebsd.org/changeset/doc/49948 Log: Remove the leading '-' from ALPHA, BETA, RC, and RELEASE for consistency. Sponsored by: The FreeBSD Foundation Modified: user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml Modified: user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml ============================================================================== --- user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml Tue Feb 7 18:24:58 2017 (r49947) +++ user/gjb/releng-rewrite/en_US.ISO8859-1/articles/freebsd-releng/article.xml Tue Feb 7 19:29:31 2017 (r49948) @@ -306,7 +306,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 <literal>-RC</literal> builds.</para> + start of the <literal>RC</literal> builds.</para> <para>Depending on the underlying set of code in question, and the overall impact the set of code has on &os; as a whole, such @@ -387,28 +387,28 @@ Builds</title> <para>Starting with the &os; 10.0-RELEASE cycle, the notion - of <quote><literal>-ALPHA</literal></quote> builds was - introduced. Unlike the <literal>-BETA</literal> and - <literal>-RC</literal> builds, <literal>-ALPHA</literal> + of <quote><literal>ALPHA</literal></quote> builds was + introduced. Unlike the <literal>BETA</literal> and + <literal>RC</literal> builds, <literal>ALPHA</literal> builds are not included in the &os; Release schedule.</para> - <para>The idea behind <literal>-ALPHA</literal> builds is to + <para>The idea behind <literal>ALPHA</literal> builds is to provide regular &os;-provided builds before the creation of the &branch.stable; branch.</para> - <para>&os; <literal>-ALPHA</literal> snapshots should be built + <para>&os; <literal>ALPHA</literal> snapshots should be built approximately once a week.</para> - <para>For the first <literal>-ALPHA</literal> build, the - <literal>BRANCH</literal> value in + <para>For the first <literal>ALPHA</literal> build, the + <varname>BRANCH</varname> value in <filename>sys/conf/newvers.sh</filename> needs to be changed from <literal>CURRENT</literal> to <literal>ALPHA1</literal>. - For subsequent <literal>-ALPHA</literal> builds, increment + For subsequent <literal>ALPHA</literal> builds, increment each <literal>ALPHA<replaceable>N</replaceable></literal> value by one.</para> <para>See <xref linkend="releng-building"/> for information on - building the <literal>-ALPHA</literal> images.</para> + building the <literal>ALPHA</literal> images.</para> </sect2> <sect2 xml:id="releng-head-freeze-kbi"> @@ -460,7 +460,7 @@ release cycle from an extablished &branch.stable; branch.</para> <sect2 xml:id="releng-stable-builds-beta"> - <title>&os; <literal>-BETA</literal> Builds</title> + <title>&os; <literal>BETA</literal> Builds</title> <para> </para> </sect2> @@ -478,13 +478,13 @@ </sect2> <sect2 xml:id="releng-release-rc"> - <title>&os; <literal>-RC</literal> Builds</title> + <title>&os; <literal>RC</literal> Builds</title> <para> </para> </sect2> <sect2 xml:id="releng-release-final"> - <title>The &os; <literal>-RELEASE</literal> Build</title> + <title>The &os; <literal>RELEASE</literal> Build</title> <para> </para> </sect2>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201702071929.v17JTVhq030815>