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 F3C4BDD3E for ; Tue, 12 Feb 2013 07:03:22 +0000 (UTC) Received: (qmail 1169 invoked by uid 500); 12 Feb 2013 07:03:22 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 1115 invoked by uid 500); 12 Feb 2013 07:03:22 -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 1105 invoked by uid 99); 12 Feb 2013 07:03:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 07:03:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of animesh.chaturvedi@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 07:03:17 +0000 X-IronPort-AV: E=Sophos;i="4.84,647,1355097600"; d="scan'208";a="6772699" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Feb 2013 07:02:32 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Mon, 11 Feb 2013 23:02:31 -0800 From: Animesh Chaturvedi To: "cloudstack-dev@incubator.apache.org" , David Nalley CC: Chip Childers , Prasanna Santhanam , Alex Huang , mice xia , Chiradeep Vittal , Meghna Kale Date: Mon, 11 Feb 2013 23:02:31 -0800 Subject: RE: Review Request: Added Unit test cases for com.cloud.api.commands Thread-Topic: Review Request: Added Unit test cases for com.cloud.api.commands Thread-Index: Ac3eH5N0tB+0zTYHTMmvm3kxbQXHSwqz1GtA Message-ID: <7A92FF96DF135843B4B608FB576BFC3E012DA42B250B@SJCPMAILBOX01.citrite.net> References: <20121212105620.7759.39423@reviews.apache.org> <20121219035920.20143.86959@reviews.apache.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Meghna While I was going through the review board I saw this was last updates over= a month ago, Do you have any updates? Animesh > -----Original Message----- > From: Rohit Yadav [mailto:rohit.yadav@citrix.com] > Sent: Wednesday, December 19, 2012 11:32 AM > To: David Nalley > Cc: cloudstack-dev@incubator.apache.org; Chip Childers; Prasanna Santhana= m; > Alex Huang; mice xia; Chiradeep Vittal; Meghna Kale > Subject: Re: Review Request: Added Unit test cases for > com.cloud.api.commands >=20 >=20 > On 19-Dec-2012, at 8:36 AM, David Nalley wrote: >=20 > > On Tue, Dec 18, 2012 at 10:59 PM, Rohit Yadav > wrote: > >> > >> ----------------------------------------------------------- > >> This is an automatically generated e-mail. To reply, visit: > >> https://reviews.apache.org/r/8545/#review14711 > >> ----------------------------------------------------------- > >> > >> > >> Thanks for your patch, but your changes are not applying cleanly and w= ill > break both api_refactoring and javelin. I will have to merge the > api_refactoring branch soon else there will be pile of review with a lot = of > merge conflicts. > >> > >> My target was to merge api_refactoring yesterday but I thought I would= fix > some more stuff before I merge it on master >=20 > See below: >=20 > >> so it won't break anything on master. > >> If you already working on some other unit tests pl. work on the > api_refactoring branch, I'm planning to send a merge request and progress > report on dev ML this weekend. > >> > >> - Rohit Yadav > >> > > > > Please discuss this on list before you attempt a merge. >=20 > Yes, as I mentioned I'll send a merge request before doing it i.e. ask co= mmunity > to checkout the code comment on merge etc. Meanwhile, any patch related t= o > api layer, anything like unit tests etc. should be done on api_refactorin= g to > avoid merge conflicts without waiting for the actual merge on master. >=20 > > Something of > > this magnitude should not happen without some degree of notice. >=20 > I understand your concern but I think it won't be any major issue as the = merge > conflicts on master (as of now) are about 100-200 and the only significan= t > changes are package renames, and annotations. >=20 > Regards. >=20 > > > > --David