Animesh, There will always be developers creating conflicts or not taking into account the semantics of other peoples code. Certainly in a worldwide project like ACS. I see your reservation. The question is if we improve the situation by working differently. I don't know but I think we will. More important is that people educate themselves on the way of working. (I am repeating myself, am I?)
regards, Daan On Sun, Aug 3, 2014 at 6:50 AM, 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 >> >> > -- Daan
