os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Replace RELENG* references with releng/* since releases are prepared

Browse source 
from svn.
This commit is contained in:
Glen Barber 2013-03-30 23:57:47 +00:00
parent 4cb7afbe14
commit 2898a4a4a9
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41327
2 changed files with 4 additions and 4 deletions
en_US.ISO8859-1/htdocs
administration.xml
releng
charter.xml

2
en_US.ISO8859-1/htdocs/administration.xml
View file

@ -143,7 +143,7 @@
<p>The Primary Release Engineering Team is responsible for setting and <p>The Primary Release Engineering Team is responsible for setting and
publishing release schedules for official project releases of FreeBSD, publishing release schedules for official project releases of FreeBSD,
announcing code freezes and maintaining <code>RELENG_*</code> branches, among other announcing code freezes and maintaining <code>releng/*</code> branches, among other
things. The <a things. The <a
href="releng/charter.html">release engineering team charter</a> href="releng/charter.html">release engineering team charter</a>
describes the duties and responsibilities of the Primary Release describes the duties and responsibilities of the Primary Release

6
en_US.ISO8859-1/htdocs/releng/charter.xml
View file

@ -29,9 +29,9 @@
change-review committee to decide which changes may be made to a change-review committee to decide which changes may be made to a
branch during a code freeze. This includes freezes for HEAD when branch during a code freeze. This includes freezes for HEAD when
approaching a .0 release as well as the traditional approaching a .0 release as well as the traditional
<tt>RELENG_*</tt> code freeze pending a -STABLE release.</p></li> <tt>releng/*</tt> code freeze pending a -STABLE release.</p></li>
<li><p>Creation and maintenance of <tt>RELENG_*</tt> branches of the <li><p>Creation and maintenance of <tt>releng/*</tt> branches of the
<tt>src/</tt> tree. This includes final authority over what <tt>src/</tt> tree. This includes final authority over what
commits are made (and remain in) the -STABLE branch prior to the commits are made (and remain in) the -STABLE branch prior to the
branching of a release branch.</p></li> branching of a release branch.</p></li>
@ -60,7 +60,7 @@
<li><p>Coordinating with the security officer team to ensure that <li><p>Coordinating with the security officer team to ensure that
pending FreeBSD releases are not affected by recently disclosed pending FreeBSD releases are not affected by recently disclosed
vulnerabilities. Also, approximately 1 week after a release, vulnerabilities. Also, approximately 1 week after a release,
change approval control of release branches (<tt>RELENG_X_Y</tt>) change approval control of release branches (<tt>releng/X.Y/</tt>)
is transfered from the release engineers to the security-officer is transfered from the release engineers to the security-officer
team. The exact transfer date is to be worked out by the two team. The exact transfer date is to be worked out by the two
parties once it is clear that the release was a success. A heads parties once it is clear that the release was a success. A heads