Add a section as a starting point for various website updates that

are needed during the release cycle.

Sponsored by:	The FreeBSD Foundation
This commit is contained in:
Glen Barber 2017-07-25 17:50:09 +00:00
parent 79613b6027
commit 27290c57e0
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=50563
2 changed files with 118 additions and 0 deletions

View file

@ -22,6 +22,7 @@
<!ENTITY release.minor.version SYSTEM "./releng-minor-version.xml">
<!ENTITY release.mirrors SYSTEM "./releng-mirrors.xml">
<!ENTITY release.terminology SYSTEM "./releng-terminology.xml">
<!ENTITY release.website SYSTEM "./releng-website.xml">
]>
<article xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
@ -108,6 +109,14 @@
</listitem>
</varlistentry>
<varlistentry>
<term><xref linkend="releng-website"/></term>
<listitem>
<para>Website Changes During the Release Cycle</para>
</listitem>
</varlistentry>
<varlistentry>
<term><xref linkend="releng-terms"/></term>
@ -421,6 +430,7 @@
</sect1>
&release.terminology;
&release.website;
&release.major.version;
&release.minor.version;
&release.building;

View file

@ -0,0 +1,108 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
<sect1 xml:id="releng-website">
<title>Website Changes During the Release Cycle</title>
<para>This section describes the changes to the website that should
occur as the release cycle progresses.</para>
<note>
<para>The files specified throughout this section are relative to
the <literal>head/</literal> branch of the
<literal>doc</literal> repository in
<application>Subversion</application>.</para>
</note>
<sect2 xml:id="releng-website-prerelease">
<title>Website Changes Before the Release Cycle Begins</title>
<para>When the release cycle schedule is available, these files
need to be updated to enable various different functionalities
on the &os;&nbsp;Project website:</para>
<informaltable frame="none" pgwide="0">
<tgroup cols="2">
<thead>
<row>
<entry>File to Edit</entry>
<entry>What to Change</entry>
</row>
</thead>
<tbody>
<row>
<entry><filename>share/xml/release.ent</filename></entry>
<entry>Change <literal>beta.upcoming</literal>
from <literal>IGNORE</literal> to <literal>INCLUDE</literal></entry>
</row>
<row>
<entry><filename>share/xml/release.ent</filename></entry>
<entry>Change <literal>%&nbsp;beta.upcoming</literal>
from <literal>IGNORE</literal> to <literal>INCLUDE</literal></entry>
</row>
<row>
<entry><filename>share/xml/release.ent</filename></entry>
<entry>Change <literal>beta.testing</literal>
from <literal>IGNORE</literal> to <literal>INCLUDE</literal></entry>
</row>
<row>
<entry><filename>share/xml/release.ent</filename></entry>
<entry>Change <literal>%&nbsp;beta.testing</literal>
from <literal>IGNORE</literal> to <literal>INCLUDE</literal></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect2>
<sect2 xml:id="releng-website-beta-rc">
<title>Website Changes During <literal>BETA</literal> or
<literal>RC</literal></title>
<para>When transitioning from <literal>PRERELEASE</literal> to
<literal>BETA</literal>, these files need to be updated to
enable the &quot;Help Test&quot; block on the download page.
All files are relative to <filename
class="directory">head/</filename> in the
<literal>doc</literal> repository:</para>
<informaltable frame="none" pgwide="0">
<tgroup cols="2">
<thead>
<row>
<entry>File to Edit</entry>
<entry>What to Change</entry>
</row>
</thead>
<tbody>
<row>
<entry><filename>en_US.ISO8859-1/htdocs/releases/11.0R/schedule.xml</filename></entry>
<entry>Change <literal>%&nbsp;beta.local.where</literal>
<literal>IGNORE</literal> to
<literal>INCLUDE</literal></entry>
</row>
<row>
<entry><filename>share/xml/release.ent</filename></entry>
<entry>Update <literal>%&nbsp;betarel.vers</literal> to
<literal>BETA<replaceable>1</replaceable></literal></entry>
</row>
<row>
<entry><filename>share/xml/news.xml</filename></entry>
<entry>Add an entry announcing the
<literal>BETA</literal></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect2>
</sect1>