Date: Mon, 23 Mar 2009 16:12:12 GMT From: Rene Ladan <rene@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 159685 for review Message-ID: <200903231612.n2NGCCGC033089@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=159685 Change 159685 by rene@rene_self on 2009/03/23 16:12:05 Minor changes to the committers guide: * ports freeze ends are also sent to ports@ * capitalize "Ports Management Team" * One instance of "VCS" seemed superfluous to me Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#17 edit Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#17 (text+ko) ==== @@ -1975,7 +1975,7 @@ <para>Discuss any significant change <emphasis>before</emphasis> committing.</para> - <para>The VCS repository is not where changes should be + <para>The repository is not where changes should be initially submitted for correctness or argued over, that should happen first in the mailing lists and the commit should only happen once something resembling consensus has @@ -2827,9 +2827,9 @@ <answer> <para>During the ports freeze, you are not allowed to commit anything to the tree without explicit approval - from the ports management team. <quote>Explicit + from the Ports Management Team. <quote>Explicit approval</quote> here means that you send a patch to - the ports management team for review and get a reply + the Ports Management Team for review and get a reply saying, <quote>Go ahead and commit it.</quote> </para> @@ -2862,7 +2862,7 @@ rolled.</para> <para>When the freeze starts, there will be another - announcement to the &a.committers;, of course.</para> + announcement to the &a.ports; and &a.committers;, of course.</para> </answer> </qandaentry>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903231612.n2NGCCGC033089>