Author: chipchilders
Date: Fri Jan  4 15:56:53 2013
New Revision: 1428940

URL: http://svn.apache.org/viewvc?rev=1428940&view=rev
Log:
added note about a bug ID being part of the review submission

Modified:
    
incubator/cloudstack/site/trunk/content/cloudstack/develop/non-contributors.mdtext

Modified: 
incubator/cloudstack/site/trunk/content/cloudstack/develop/non-contributors.mdtext
URL: 
http://svn.apache.org/viewvc/incubator/cloudstack/site/trunk/content/cloudstack/develop/non-contributors.mdtext?rev=1428940&r1=1428939&r2=1428940&view=diff
==============================================================================
--- 
incubator/cloudstack/site/trunk/content/cloudstack/develop/non-contributors.mdtext
 (original)
+++ 
incubator/cloudstack/site/trunk/content/cloudstack/develop/non-contributors.mdtext
 Fri Jan  4 15:56:53 2013
@@ -65,7 +65,7 @@ Click <strong>Create Review Request</str
 
 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.")
 
-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.
+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 ).
 
 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. 
 


Reply via email to