svn commit: r844967 - in /websites/staging/cloudstack/trunk/content: ./ cloudstack/develop/non-contributors.html

[bu...@apache.org]

Author: buildbot
Date: Fri Jan  4 15:57:04 2013
New Revision: 844967

Log:
Staging update by buildbot for cloudstack

Modified:
    websites/staging/cloudstack/trunk/content/   (props changed)
    websites/staging/cloudstack/trunk/content/cloudstack/develop/non-contributors.html

Propchange: websites/staging/cloudstack/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan  4 15:57:04 2013
@@ -1 +1 @@
-1428527
+1428940

Modified: websites/staging/cloudstack/trunk/content/cloudstack/develop/non-contributors.html
==============================================================================
--- websites/staging/cloudstack/trunk/content/cloudstack/develop/non-contributors.html (original)
+++ websites/staging/cloudstack/trunk/content/cloudstack/develop/non-contributors.html Fri Jan  4 15:57:04 2013
@@ -163,7 +163,7 @@
 <li>Testing Done</li>
 </ul>
 <p>The <strong>Summary</strong> will be the subject that's sent to the cloudstack-dev mailing list. So if your summary is "fixed feature foo" the subject of the mail sent to the list will be "Review Request: fixed feature foo". Try to be descriptive with the Summary. If you're submitting a patch for a bug, please be sure to include the bug number in the summary. (Like "Bugfix CS-15942: Fixing problem with redundant routers.")</p>
-<p>The description should be a full description of what you've done. Please be specific, and include enough information that any reviewer will be able to look at your patch without asking for follow-up information.</p>
+<p>The description should be a full description of what you've done. Please be specific, and include enough information that any reviewer will be able to look at your patch without asking for follow-up information.   You need to include the bug ID that your patch relates to as well (ex:  CLOUDSTACK-XXX ).</p>
 <p>If you're submitting a patch that modifies code, adds features, etc. you should test before submitting. Please be sure to describe your tests here. </p>
 <p>Once you're sure everything is OK, go ahead and submit the patch. But that's <em>not</em> the end of the process. The work isn't done until the patch is committed!</p>
 <h2 id="review">Review</h2>