[Cruisecontrol-checkins] CVS: cruisecontrol/docs contributions.html,1.15,1.16

[Jeffrey F. <jfr...@us...>]

Update of /cvsroot/cruisecontrol/cruisecontrol/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7738

Modified Files:
	contributions.html 
Log Message:
updated to mention the JIRA and to reinforce the desire for unit tests, etc

Index: contributions.html
===================================================================
RCS file: /cvsroot/cruisecontrol/cruisecontrol/docs/contributions.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- contributions.html	6 Oct 2005 07:41:39 -0000	1.15
+++ contributions.html	25 Apr 2006 07:42:37 -0000	1.16
@@ -52,12 +52,11 @@
 
         <h2>Making Contributions</h2>
 
-        <p>Contributions should be mailed to the Developer <a href="contact.html">
-        mailing list</a>. (Here is a discussion of why the SourceForge provided
-        <a href="sffeatures.html">tracking features are not used</a>.) The
-        contribution may be a patch or an entire file as an attachment. A
-        Committer will include the contribution in the repository. Not every
-        contribution will be committed to the repository.</p>
+        <p>Contributions should be submitted to the <a href="http://jira.public.thoughtworks.org/browse/CC">JIRA
+        issue tracking site</a>. Simple contributions may alternatively be mailed to
+        the <a href="developers.html">Developer mailing list</a>. (Here is a
+        discussion of why the SourceForge provided <a href="sffeatures.html">tracking
+        features are not used</a>.)</p>
 
         <p>The Committer must analyze the contribution to make sure that it
         conforms to the overall project vision. If the Committer questions the
@@ -73,13 +72,15 @@
         <ul>
           <li>a description of what problem the contribution solves</li>
           <li>modification to existing files in the form of a unified diff
-          (<pre>cvs diff -u</pre>)</li>
+          <pre>cvs diff -u</pre></li>
           <li>unit tests for any code</li>
           <li>documentation changes for any new or modified behavior</li>
         </ul>
 
         <p>These elements are not required, but they are very much
-        appreciated!</p>
+        appreciated! Failure to provide them will likely lengthen the
+        review and commit cycle due to the extra burden on the committers
+        to supply the lack.</p>
 
         <h2>Acknowledgment</h2>