Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of dhkakadia@gmail.com designates
 209.85.216.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALxDHnnMrTwDmrvW3X47nkKLugKQdGiKOdRGEXWv7jPb6Xo_QQ@mail.gmail.com>
References: 
 <CALxDHnnHSB8=DpwzDyAAvipnejnV2vtZ1gjt_8-CZitfcQoHew@mail.gmail.com>
 <20130507193801.GE10900@USLT-205755.sungardas.corp>
 <CALxDHnnDP-3_EkiWfK0hwgv6UV-9YNgR-OYK2idh-a5CwQ2qBg@mail.gmail.com>
 <20130508133052.GI33720@USLT-205755.sungardas.corp>
 <7A92FF96DF135843B4B608FB576BFC3E01431C133B0C@SJCPMAILBOX01.citrite.net>
 <CALxDHnmdZPK19_hK5ET61GE+FqHQHB_ASJOrh5G9pOU-24zdGw@mail.gmail.com>
 <CAKprHVaNXWxRXTnECQ+vJRJ7aQmUCBNp9Zg16tZk+pw9S=GoQQ@mail.gmail.com>
 <CALxDHnnMrTwDmrvW3X47nkKLugKQdGiKOdRGEXWv7jPb6Xo_QQ@mail.gmail.com>
From: Dharmesh Kakadia <dhkakadia@gmail.com>
Date: Thu, 27 Jun 2013 22:53:29 +0530
Message-ID: 
 <CALxDHnk0b-+hBZuVKFjYiwwS+aOZA=ci1wN=5-f2HLuEc8daZQ@mail.gmail.com>
Subject: Re: Suggestion needed for CLOUDSTACK-212
To: dev <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=047d7bf0e06c865de204e026066d

--047d7bf0e06c865de204e026066d
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I misunderstood the feature freeze. This has been assigned to fix in
Version 4.2 on jira. As per this discussion, should I change it to 4.3 ?

Thanks,
Dharmesh


On Sat, May 11, 2013 at 10:13 AM, Dharmesh Kakadia <dhkakadia@gmail.com>wrote:

> ok. great.
>
> Thanks,
> Dharmesh
>
>
> On Sat, May 11, 2013 at 5:53 AM, David Nalley <david@gnsa.us> wrote:
>
>> Dharmesh:
>>
>> Thanks for tackling this - I imagine there might be a little bit of churn,
>> as features finally land in master, but shouldn't be much - I may pull
>> this
>> into a feature branch, and we can routinely rebase and see where we stand.
>>
>> Thanks for being patient and flexible.
>>
>> --David
>>
>> On Friday, May 10, 2013, Dharmesh Kakadia wrote:
>>
>> > Just saw this. I have done the refactoring and code is available at
>> >
>> >
>> https://github.com/dharmeshkakadia/incubator-cloudstack/tree/com.cloud-to-org.apache-refactoringto
>> > try. In case we want to do it after 4.2-freeze, I am ready to redo it.
>> >
>> > Thanks,
>> > Dharmesh
>> >
>> >
>> > On Fri, May 10, 2013 at 3:28 AM, Animesh Chaturvedi <
>> > animesh.chaturvedi@citrix.com <javascript:;>> wrote:
>> >
>> > >
>> > >
>> > > > -----Original Message-----
>> > > > From: Chip Childers [mailto:chip.childers@sungard.com<javascript:;>]
>> > > > Sent: Wednesday, May 08, 2013 6:31 AM
>> > > > To: dev@cloudstack.apache.org <javascript:;>
>> > > > Subject: Re: Suggestion needed for CLOUDSTACK-212
>> > > >
>> > > > Dharmesh,
>> > > >
>> > > > I'd also suggest that you actually plan on submitting this after the
>> > 4.2
>> > > feature
>> > > > freeze, to be included in 4.3.  This is the type of change that has
>> > > bitten us
>> > > > with almost every release...  and doing it close to the end of the
>> > merge
>> > > > window may not be a good idea.  Our general preference is to do
>> these
>> > > types
>> > > > of changes in master right *after* the latest feature release has
>> it's
>> > > branch
>> > > > cut.
>> > > >
>> > > > -chip
>> > > [Animesh>] yes 4.2 freeze is just 3 weeks out. This can be merged into
>> > > master in early June
>> > > >
>> > > > On Wed, May 08, 2013 at 10:29:22AM +0530, Dharmesh Kakadia wrote:
>> > > > > ok. I will go with that.
>> > > > >
>> > > > > Thanks,
>> > > > > Dharmesh
>> > > > >
>> > > > > On Wed, May 8, 2013 at 1:08 AM, Chip Childers
>> > > > <chip.childers@sungard.com <javascript:;>>wrote:
>> > > > >
>> > > > > > On Tue, May 07, 2013 at 11:14:12PM +0530, Dharmesh Kakadia
>> wrote:
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > I am trying to move java package structure from com.cloud to
>> > > > > > > org.apache (
>> > > > > > > https://issues.apache.org/jira/browse/CLOUDSTACK-212). I am
>> > > > thinking of doing it the following way (Totally newbie), needed
>> > feedback
>> > > on
>> > > > that.
>> > > > > > >
>> > > > > > > 1. grep "com.cloud" on the entire repo.
>> > > > > > > 2. update all package declarations using eclipse.
>> > > > > > > 3. Update scripts etc found in 1 manually.
>> > > > > > >
>> > > > > > > Will it be a good way to do it ? Any better suggestion ?
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > > Dharmesh
>> > > > > >
>> > > > > > That seems like a reasonable approach.  We will probably want to
>> > > > > > create a branch when you submit a patch for this, and apply it
>> > > > > > there...  just to spend some time ensuring that the changes
>> work.
>> > > > > >
>> > > > > > -chip
>> > > > > >
>> > >
>> >
>>
>
>

--047d7bf0e06c865de204e026066d--