Date: Sat, 30 Mar 2013 23:57:47 +0000 (UTC) From: Glen Barber <gjb@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r41327 - in head/en_US.ISO8859-1/htdocs: . releng Message-ID: <201303302357.r2UNvl39017714@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: gjb Date: Sat Mar 30 23:57:47 2013 New Revision: 41327 URL: http://svnweb.freebsd.org/changeset/doc/41327 Log: Replace RELENG* references with releng/* since releases are prepared from svn. Modified: head/en_US.ISO8859-1/htdocs/administration.xml head/en_US.ISO8859-1/htdocs/releng/charter.xml Modified: head/en_US.ISO8859-1/htdocs/administration.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/administration.xml Sat Mar 30 21:29:50 2013 (r41326) +++ head/en_US.ISO8859-1/htdocs/administration.xml Sat Mar 30 23:57:47 2013 (r41327) @@ -143,7 +143,7 @@ <p>The Primary Release Engineering Team is responsible for setting and 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 href="releng/charter.html">release engineering team charter</a> describes the duties and responsibilities of the Primary Release Modified: head/en_US.ISO8859-1/htdocs/releng/charter.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releng/charter.xml Sat Mar 30 21:29:50 2013 (r41326) +++ head/en_US.ISO8859-1/htdocs/releng/charter.xml Sat Mar 30 23:57:47 2013 (r41327) @@ -29,9 +29,9 @@ change-review committee to decide which changes may be made to a branch during a code freeze. This includes freezes for HEAD when 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 commits are made (and remain in) the -STABLE branch prior to the branching of a release branch.</p></li> @@ -60,7 +60,7 @@ <li><p>Coordinating with the security officer team to ensure that pending FreeBSD releases are not affected by recently disclosed 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 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303302357.r2UNvl39017714>