Author: buildbot
Date: Thu Jun 5 19:24:47 2014
New Revision: 911478
Log:
Staging update by buildbot for mahout
Modified:
websites/staging/mahout/trunk/content/ (props changed)
websites/staging/mahout/trunk/content/developers/github.html
Propchange: websites/staging/mahout/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 5 19:24:47 2014
@@ -1 +1 @@
-1600722
+1600732
Modified: websites/staging/mahout/trunk/content/developers/github.html
==============================================================================
--- websites/staging/mahout/trunk/content/developers/github.html (original)
+++ websites/staging/mahout/trunk/content/developers/github.html Thu Jun 5
19:24:47 2014
@@ -336,7 +336,15 @@ would warn to begin with. Anyway, watch
<p>that should close PR <code>ZZ</code> on github mirror without merging and
any code modifications in the master repository.</p>
<h2 id="apachegithub-integration-features">Apache/github integration
features</h2>
-<p>Read [<a
href="https://blogs.apache.org/infra/entry/improved_integration_between_apache_and";>4</a>].
Comments (and PRs?) with Mahout issue handles should post to mailing lists and
Jira.</p>
+<p>Read [<a
href="https://blogs.apache.org/infra/entry/improved_integration_between_apache_and";>4</a>].
Comments and PRs with Mahout issue handles should post to mailing lists and
Jira.
+Mahout issue handles must in the form MAHOUT-YYYYY (all capitals). Usually it
makes sense to
+file a jira issue first, and then create a PR with description </p>
+<div class="codehilite"><pre><span class="n">MAHOUT</span><span
class="o">-</span><span class="n">YYYY</span><span class="p">:</span> <span
class="o"><</span><span class="n">jira</span><span class="o">-</span><span
class="n">issue</span><span class="o">-</span><span
class="n">description</span><span class="o">></span>
+</pre></div>
+
+
+<p>In this case all subsequent comments will automatically be copied to jira
without having to mention
+jira issue explicitly in each comment of the PR.</p>
</div>
</div>
</div>
