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.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALxDHn=w+jjvfV1Of1zdbK7EgX6ADw4EdDar3J2ANzi8q72F7Q@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>
 <244783D9-4F29-4C41-BBCB-21C82C218A00@gmail.com>
 <CALxDHn=w+jjvfV1Of1zdbK7EgX6ADw4EdDar3J2ANzi8q72F7Q@mail.gmail.com>
From: Dharmesh Kakadia <dhkakadia@gmail.com>
Date: Thu, 9 May 2013 16:54:35 +0530
Message-ID: 
 <CALxDHnnCPFunbHSUjgOvu+EbkvjQ8iPYMgAYN7voUUJMJPqMbw@mail.gmail.com>
Subject: Re: Suggestion needed for CLOUDSTACK-212
To: dev <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=00032557fa1ecbc55704dc474cc0

--00032557fa1ecbc55704dc474cc0
Content-Type: text/plain; charset=ISO-8859-1

I have finished the refactoring (ran into eclipse refactoring bugs). I am
now trying to test. But I realized that it will be good to have tool/script
that does most of this refactoring rather than using eclipse. Anyone knows
any such tool/script ? Otherwise I plan to make one.

Thanks,
Dharmesh


On Wed, May 8, 2013 at 9:08 PM, Dharmesh Kakadia <dhkakadia@gmail.com>wrote:

> I have started refactoring !! I am planning to finish refactoring by
> tomorrow. I will then need help and guidance in doing testing,branching
> etc. Let's try this out !!
>
> Thanks,
> Dharmesh
>
>
> On Wed, May 8, 2013 at 7:20 PM, Sebastien Goasguen <runseb@gmail.com>wrote:
>
>>
>> On May 8, 2013, at 9:30 AM, Chip Childers <chip.childers@sungard.com>
>> wrote:
>>
>> > 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
>>
>> To add to that, feature freeze for 4.2 is scheduled to be 5/31.
>>
>> We could have your code in a feature branch before that, and merge it
>> early june. It would then be included in 4.3
>>
>>
>>
>> >
>> > 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>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
>> >>>
>>
>>
>

--00032557fa1ecbc55704dc474cc0--