Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 499C292E0 for ; Wed, 4 Jul 2012 04:25:31 +0000 (UTC) Received: (qmail 84540 invoked by uid 500); 4 Jul 2012 04:25:31 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 84513 invoked by uid 500); 4 Jul 2012 04:25:30 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 84485 invoked by uid 99); 4 Jul 2012 04:25:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2012 04:25:30 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [123.124.189.193] (HELO mail.cloud-valley.com) (123.124.189.193) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2012 04:25:24 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Subject: Re: about patch submit Date: Wed, 4 Jul 2012 12:25:23 +0800 Message-ID: <2C97F788CCC013428671BC3A5FC2F64D412A@c-mail.cloud-valley.com.cn> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: about patch submit Thread-Index: Ac1Y1363KCrBN0R9QcO5LIAs5HNB9QAsmlMwAAFcHZAAAxLA8A== References: <2C97F788CCC013428671BC3A5FC2F64D411E@c-mail.cloud-valley.com.cn> <67EF18FDCA335F489B366120481AB6C5EE3AD43AFF@BANPMAILBOX01.citrite.net> From: "Mice Xia" To: X-Virus-Checked: Checked by ClamAV on apache.org Pranav, Thanks for your detailed reply. One more thing, if I want to file a bug in http://bugs.cloudstack.org, = one of the required fields is 'affect versions', I wonder which one = corresponds to branch 3.0.x? is that 3.0.4? Regards Mice -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: Pranav Saxena [mailto:pranav.saxena@citrix.com]=20 =B7=A2=CB=CD=CA=B1=BC=E4: 2012=C4=EA7=D4=C24=C8=D5 10:59 =CA=D5=BC=FE=C8=CB: cloudstack-dev@incubator.apache.org =B3=AD=CB=CD: Mice Xia =D6=F7=CC=E2: RE: about patch submit 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+worl= d Procedure for submitting a patch through Review Board Tool -=20 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 -=20 2.1) - Click on New Review Request=20 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 -=20 3.1) - Branch - The name of apache branch you are working on ( = 3.0.x /Master)=20 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_xia@tcloudcomputing.com]=20 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