From 9e25d122028826b9d23cc76dbb842599fb3b84a3 Mon Sep 17 00:00:00 2001 From: Mathieu Arnold Date: Tue, 16 Aug 2016 12:29:48 +0000 Subject: [PATCH] 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 --- .../articles/committers-guide/article.xml | 63 +++++++++++++++++++ 1 file changed, 63 insertions(+) diff --git a/en_US.ISO8859-1/articles/committers-guide/article.xml b/en_US.ISO8859-1/articles/committers-guide/article.xml index fa9cf2fed6..93fa026a2a 100644 --- a/en_US.ISO8859-1/articles/committers-guide/article.xml +++ b/en_US.ISO8859-1/articles/committers-guide/article.xml @@ -4820,6 +4820,69 @@ Do you want to commit? (no = start a shell) [y/n] + + + + How can an experimental test build of the ports tree + (exp-run) be requested? + + + + 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. + + Full package builds will be done with the patches + provided by the submitter, and the submitter is required + to fix detected problems (fallout) + before commit. + + + + Go to the Bugzilla + new PR page. + + + + Select the product your patch is about. + + + + Fill in the bug report as normal. Remember to + attach the patch. + + + + If at the top it says Show Advanced + Fields click on it. It will now say + Hide Advanced Fields. Many new + fields will be available. If it already says + Hide Advanced Fields, no need to do + anything. + + + + In the Flags section, set the + exp-run one to ?. + As for all other fields, hovering the mouse over any + field shows more details. + + + + Submit. + + + + 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. + + + +