The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: row/entry
Context English State
Update <literal>LLD_REVISION_STRING</literal>
Update <literal>LILB32CPUFLAGS</literal>
Release from <literal>stable/</literal>
This section describes the general procedures of the FreeBSD release cycle from an extablished <literal>stable/</literal> branch.
FreeBSD <literal>stable</literal> Branch Code Slush
In preparation for the code freeze on a <literal>stable</literal> branch, several files need to be updated to reflect the release cycle is officially in progress. These files are all relative to the top-most level of the stable branch:
Update the <varname>BRANCH</varname> value to reflect <literal>PRERELEASE</literal>
Update <varname>TARGET_TRIPLE</varname>
Update <varname>OS_VERSION</varname>
Update <literal>LIB32CPUFLAGS</literal>
Add a new <literal>.ds</literal> entry for the FreeBSD version, and update <varname>doc-default-operating-system</varname> (FreeBSD 11.x and earlier only)
In the <literal>doc</literal> repository, also update <filename>head/en_US.ISO8859-1/htdocs/releases/<replaceable>12.0</replaceable>R/Makefile.hardware</filename>, switching the value of <varname>_BRANCH</varname> to <literal>BETA<replaceable>X</replaceable></literal>, <literal>RC<replaceable>X</replaceable></literal>, or <literal>RELEASE</literal>, respectively.
FreeBSD <literal>BETA</literal> Builds
Following the code slush, the next phase of the release cycle is the code freeze. This is the point at which all commits to the stable branch require explicit approval from the FreeBSD Release Engineering Team. This is enforced by pre-commit hooks in the Subversion repository by editing <filename>base/svnadmin/conf/approvers</filename> to include a regular expression matching the <literal>stable/<replaceable>12</replaceable>/</literal> branch for the release:
^/<literal>stable/<replaceable>12</replaceable>/</literal> re
^/<literal>releng/<replaceable>12.0</replaceable>/</literal> re
There are two general exceptions to requiring commit approval during the release cycle. The first is any change that needs to be committed by the Release Engineer in order to proceed with the day-to-day workflow of the release cycle, the other is security fixes that may occur during the release cycle.
Once the code freeze is in effect, the next build from the branch is labeled <literal>BETA1</literal>. This is done by updating the <varname>BRANCH</varname> value in <filename>sys/conf/</filename> from <literal>PRERELEASE</literal> to <literal>BETA1</literal>.
Once this is done, the first set of <literal>BETA</literal> builds are started. Subsequent <literal>BETA</literal> builds do not require updates to any files other than <filename>sys/conf/</filename>, incrementing the <literal>BETA</literal> build number.
Creating the <literal>releng/<replaceable>12.0</replaceable>/</literal> Branch
When the first <literal>RC</literal> (Release Candidate) build is ready to begin, the <literal>releng/</literal> 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 <varname>__FreeBSD_version</varname> values, for example. The paths listed below are relative to the repository root. The order of commits and what to change are:
<prompt>%</prompt> <userinput>svn cp ^/<literal>stable/<replaceable>12</replaceable>/</literal> <literal>releng/<replaceable>12.0</replaceable>/</literal></userinput>
Change <literal>BETA<replaceable>X</replaceable></literal> to <literal>RC1</literal>


New source string 8 months ago
Browse all component changes

Source information

Source string comment
(itstool) path: row/entry
Source string location
String age
8 months ago
Source string age
8 months ago
Translation file
articles/freebsd-releng.pot, string 194