Source string Read only

(itstool) path: row/entry
Context English State
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.



New source string

FreeBSD Doc / articles_freebsd-relengEnglish

New source string 3 months ago
Browse all component changes


English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: row/entry
No labels currently set.
Source string location
Source string age
3 months ago
Translation file
, string 196