Hi Hugo, Its mainly to get an opinion on the proposal. I am expecting all the active committers to take a look at it and raise any concerns they have.
If we don’t get any -1’s or edits, we should start on it. Post voting, if its approved, we should do the required git branch changes as suggested in the proposal and all the new checkins are expected to follow the new commit flow for 4.5+. if its not approved, we are either happy with the existing flow or we will have some good suggestions with which we may need to start a vote again. ~Rajani On 31-Jul-2014, at 4:13 pm, Hugo Trippaers <h...@trippaers.nl> wrote: > Rajani, > > To make it clear for everyone. This is the vote to adopt this new way of > working right? Or is it just to get an opinion on the proposal? > > If it is indeed the vote to adopt this way of working it means that all > committers will change how we interact with the branches in the CloudStack > git. > > It’s is a good thing in my book, but we need to be clear what the expected > result is when this vote has concluded in 72 hours. > > Cheers, > > Hugo > > > On 31 jul. 2014, at 12:28, Rajani Karuturi <rajani.karut...@citrix.com> wrote: > >> 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 >> >> >> >
