svn commit: r49289 - head/en_US.ISO8859-1/articles/committers-guide

[Mathieu Arnold]

Author: mat
Date: Tue Aug 16 12:29:48 2016
New Revision: 49289
URL: https://svnweb.freebsd.org/changeset/doc/49289

Log:
  Document how to ask for an exp-run.
  
  It seems that people do not find the exp-run flag when opening a PR.
  
  Reviewed by:	bcr, wblock
  Sponsored by:	Absolight
  Differential Revision:	https://reviews.freebsd.org/D7503

Modified:
  head/en_US.ISO8859-1/articles/committers-guide/article.xml

Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/committers-guide/article.xml	Tue Aug 16 12:18:14 2016	(r49288)
+++ head/en_US.ISO8859-1/articles/committers-guide/article.xml	Tue Aug 16 12:29:48 2016	(r49289)
@@ -4820,6 +4820,69 @@ Do you want to commit? (no = start a she
 	    </tip>
 	  </answer>
 	</qandaentry>
+
+	<qandaentry xml:id="ports-exp-run">
+	  <question>
+	    <para>How can an experimental test build of the ports tree
+	      (<emphasis>exp-run</emphasis>) be requested?</para>
+	  </question>
+
+	  <answer>
+	    <para>An exp-run must be completed before patches with a
+	      significant ports impact are committed.  The patch can
+	      be against the ports tree or the base system.</para>
+
+	    <para>Full package builds will be done with the patches
+	      provided by the submitter, and the submitter is required
+	      to fix detected problems (<emphasis>fallout</emphasis>)
+	      before commit.</para>
+
+	    <procedure>
+	      <step>
+		<para>Go to the <link
+		    xlink:href="https://bugs.freebsd.org/submit">Bugzilla
+		    new <acronym>PR</acronym> page</link>.</para>
+	      </step>
+
+	      <step>
+		<para>Select the product your patch is about.</para>
+	      </step>
+
+	      <step>
+		<para>Fill in the bug report as normal.  Remember to
+		  attach the patch.</para>
+	      </step>
+
+	      <step>
+		<para>If at the top it says <quote>Show Advanced
+		    Fields</quote> click on it.  It will now say
+		  <quote>Hide Advanced Fields</quote>.  Many new
+		  fields will be available.  If it already says
+		  <quote>Hide Advanced Fields</quote>, no need to do
+		  anything.</para>
+	      </step>
+
+	      <step>
+		<para>In the <quote>Flags</quote> section, set the
+		  <quote>exp-run</quote> one to <literal>?</literal>.
+		  As for all other fields, hovering the mouse over any
+		  field shows more details.</para>
+	      </step>
+
+	      <step>
+		<para>Submit.</para>
+	      </step>
+
+	      <step>
+		<para>When the &a.portmgr; replies, fix the fallout.
+		  The fallout might be a bug in the original patch or
+		  other ports that need to be fixed.  Both need to be
+		  addressed.  Update the patch to repair all the
+		  fallout and repeat.</para>
+	      </step>
+	    </procedure>
+	  </answer>
+	</qandaentry>
       </qandadiv>
     </qandaset>
   </sect1>