On Aug 5, 2014, at 2:33 PM, Jessica Wang <jessica.w...@citrix.com> wrote:
> Exactly. This just shifts pain from one branch to another. > I don't see any gains from this, either. > I vote "-1". > It is much more than shifting pains, the wiki page is not discussion the workflow quite extensively, with several pointers that we should all take the time to view/read: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git > Jessica > > > -----Original Message----- > From: Min Chen [mailto:min.c...@citrix.com] > Sent: Tuesday, August 05, 2014 11:27 AM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] git workflow > > Agree with Animesh. Didn't see any gains from this, we just shift pain > from one branch to another, so vote -1. > > -min > > On 8/2/14 9:50 PM, "Animesh Chaturvedi" <animesh.chaturv...@citrix.com> > wrote: > >> +0 >> >> While this protects master with only commits which are merges from >> release branch and keeps it clean but the issues that we have shift to >> develop branch. >> >> >>> -----Original Message----- >>> From: Rajani Karuturi [mailto:rajani.karut...@citrix.com] >>> Sent: Thursday, July 31, 2014 3:28 AM >>> To: dev >>> Subject: [VOTE] git workflow >>> >>> Hi All, >>> >>> We had long discussions on the git flow. >>> I tried to capture the summary of it @ >>> http://markmail.org/message/j5z7dxjcqxfkfhpj >>> This is updated on wiki @ >>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git#Git- >>> ProposedGitflowbasedCheck-inProcess and is up for a vote: >>> >>> Can you share your opinion on the proposal? >>> >>> [ ] +1 approve >>> [ ] +0 no opinion >>> [ ] -1 disapprove (and reason why) >>> >>> >>> Thanks, >>> ~Rajani >>> >>> >> >
