mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r892197 - in /websites/staging/mahout/trunk/content: ./ developers/issue-tracker.html
Date Mon, 30 Dec 2013 21:41:00 GMT
Author: buildbot
Date: Mon Dec 30 21:40:59 2013
New Revision: 892197

Log:
Staging update by buildbot for mahout

Modified:
    websites/staging/mahout/trunk/content/   (props changed)
    websites/staging/mahout/trunk/content/developers/issue-tracker.html

Propchange: websites/staging/mahout/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 30 21:40:59 2013
@@ -1 +1 @@
-1554319
+1554323

Modified: websites/staging/mahout/trunk/content/developers/issue-tracker.html
==============================================================================
--- websites/staging/mahout/trunk/content/developers/issue-tracker.html (original)
+++ websites/staging/mahout/trunk/content/developers/issue-tracker.html Mon Dec 30 21:40:59
2013
@@ -350,25 +350,25 @@
   <div id="content-wrap" class="clearfix">
    <div id="main">
     <h1 id="issue-tracker">Issue tracker</h1>
-<p>Anything that is to be added to <a href="http://svn.apache.org/viewvc/mahout/">the
source code repository</a>
- is first presented as a patch in the issue tracker. All conversations are
+<ul>
+<li><a href="http://issues.apache.org/jira/browse/MAHOUT">Mahout issue tracker</a></li>
+</ul>
+<p>For most changes (apart from trivial stuff) Mahout works according to a review-then-commit
model.
+This means anything that is to be added to <a href="http://svn.apache.org/viewvc/mahout/">the
source code repository</a>
+ is first presented as a patch in the issue tracker. All conversations in the issue tracker
are automatically
 echoed on the developer mailing list and people tend to respond or continue
 conversations there rather in the issue tracker, so in order to follow an
-issue you might also have to read to the mailing lists. </p>
+issue you might also have to read to the <a href="http://mahout.apache.org/general/mailing-lists,-irc-and-archives.html">mailing
lists</a>. </p>
 <p>An issue does not literally have to be an issue. It could be a wish, task,
 bug report, etc. and it does not have to contain a patch.</p>
-<p>Mahout use <a href="http://issues.apache.org/jira/browse/MAHOUT">JIRA</a>
-. It is made by the same company that made this Wiki and a handful of other
-collaborate software development tools that supposedly can communicate with
-each other and be trigged by actions such as commits to SVN with issue
-identity in the comments.</p>
+<p>Mahout uses <a href="https://confluence.atlassian.com/display/JIRA/JIRA+Documentation">JIRA</a>
by Atlassian.</p>
 <p><a name="IssueTracker-Bestpractise"></a></p>
 <h3 id="best-practise">Best practise</h3>
 <p>Don't create duplicate issues. Make sure your problem is a problem and that
 nobody else already fixed it. If you are new to the project it is often
-prefered that the subject of an issue is discussed on one of our mailing
-list before an issue is created.</p>
-<p>Quote what it is you are responding to in comments.</p>
+preferred that the subject of an issue is discussed on one of our mailing
+list before an issue is created - in particular when it comes to adding new functionality.</p>
+<p>Quote only what it is you are responding to in comments.</p>
 <p>Patches should be created at trunk or trunk parent level and if possible be
 a single uncompressed text file so it is easy to inspect the patch in a web
 browser. (See <a href="patch-check-list.html">Patch Check List</a>
@@ -377,6 +377,10 @@ browser. (See <a href="patch-check-list.
 "MAHOUT-n" and not "mahout-n" or "n". MAHOUT-1 would automatically be
 linked to <a href="http://issues.apache.org/jira/browse/MAHOUT-1">MAHOUT-1</a>
  in a better world.</p>
+<p>A note to committers: Make sure to mention the issue id in each commit. Not only
has
+JIRA the capability of auto-linking commits to the issue they are related to
+that way, it also makes it easier to get further information for a specific commit
+when browsing through the commit log and within the commit mailing list.</p>
    </div>
   </div>     
 </div> 



Mime
View raw message