> -----Original Message-----
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Wednesday, May 08, 2013 6:31 AM
> To: dev@cloudstack.apache.org
> 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.child...@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
> > >
