Hi Mice,

To submit a patch , you might want to go through this document once -  
http://wiki.cloudstack.org/display/dev/Git+workflow+in+the+brave+new+world

Procedure for submitting a patch through Review Board Tool - 

1) Then once you have generated your patch and applied to apache branch(say 
3.0.x) , you can go to the review board tool ( https://reviews.apache.org ) to 
create a new Review request. You'll need to create your account here and then 
login to your dashboard.
2) To create a new service request , you need to do the following - 
     2.1) - Click on New Review Request 
     2.2) - Choose the repository as - cloudstack-git
     2.3) - Upload your patch where the "Diff"  label is mentioned .  You can 
leave the "Parent Diff" label empty and click on "Create Review Request".
3) Once this is done , you need to choose - 
     3.1) - Branch - The name of apache branch you are working on ( 3.0.x 
/Master) 
    3.2) - Specify the bug ticket number against "Bugs" label
     3.3) - Choose groups as "cloustack" which will automatically send an email 
to cloudstack-dev list for your patch review.
     3.4) - Similarly you can specify specific people under the "Peoples" label 
, in case you want anyone in particular to review your patch.
     3.5) - Mention the details under the description , summary , Testing done  
labels.
4) Finally click on publish to send the patch for review. You'll see an email 
being sent to the cloudstack group , the specific people you added and yourself.

Let me know in case you have any problems while submitting patches.

Thanks & Regards,
Pranav

-----Original Message-----
From: Mice Xia [mailto:mice_...@tcloudcomputing.com] 
Sent: Wednesday, July 04, 2012 7:55 AM
To: cloudstack-dev@incubator.apache.org
Subject: about patch submit

Dears,

During trying Cloudstack 3.0.x branch I found some minor bugs, and I would like 
to submit patches. Can someone tell me the workflow of submitting a patch?
Such as
* Should I file a bug in JIRA?
* Where should I post the patch, in mail list or somewhere else?
* Which branch should I target for?
* Any other things need to pay attention?


Regards
Mice

Reply via email to