Well I take it back, I think it is easier to add the path now in master
> -----Original Message-----
> From: Min Chen [mailto:min.c...@citrix.com]
> Sent: Friday, October 11, 2013 6:05 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Add upgrade path from 4.2.1 to 4.3.0 in Master
> branch
>
> Then what should we do to cherry-pick some commits from 4.2.1 to master?
> No cherry-pick until 4.3 is cut?
>
> Thanks
> -min
>
> On 10/11/13 5:25 PM, "Animesh Chaturvedi"
> <animesh.chaturv...@citrix.com>
> wrote:
>
> >> -----Original Message-----
> >> From: Min Chen [mailto:min.c...@citrix.com]
> >> Sent: Friday, October 11, 2013 4:51 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: [DISCUSS] Add upgrade path from 4.2.1 to 4.3.0 in Master
> >> branch
> >>
> >> Hi there,
> >>
> >> Based on my understanding, 4.2.1 is scheduled to come before 4.3.0
> >> release.
> >[Animesh>] Yes based on Abhi's proposal If this is true, should we add
> >an upgrade path from 4.2.1 to
> >> 4.3.0 in Master?
> >[Animesh>] Should we wait until we cut 4.3 from master. I will publish
> >the schedule for 4.3 soon
> >
> >This will help us to cherry-pick some commits done in
> >> 4.2.1 branch that involves schema changes to master. Any objections
> >> on this? If not, what will be the recommended way to cherry-pick
> >> those commits to Master? Merging schema change into schema-
> 420to430.sql?
> >>
> >> Thanks
> >> -min
> >
