[mailto:rohit.ya...@shapeblue.com]
>> Sent: Tuesday, 5 August 2014 3:20 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: NO commits to master
>>
>> Hi Rajani,
>>
>> Thanks for taking the initiative, people may still keep pushing onto master,
>> so please give the
hrs window and discard
> the current develop branch. That is much more simpler.
>
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Tuesday, 5 August 2014 3:20 PM
> To: dev@cloudstack.apache.org
> Subject: Re: NO commits to master
>
commits to master
Hi Rajani,
Thanks for taking the initiative, people may still keep pushing onto master, so
please give them a window of 24-48 hours so that everyone is informed, or
alternatively you may sync commits from master to develop but I hope we don't
end up in branch based split-
we had enough time since the vote passed. But, I agree we should have decided
on dates.
master/develop are in sync right now. So, it should be a simple branch switch
to develop and push.
some automated things like jenkins may need changes. other than that, I don’t
see any issues.
A git hook i
Hi Rajani,
Thanks for taking the initiative, people may still keep pushing onto master, so
please give them a window of 24-48 hours so that everyone is informed, or
alternatively you may sync commits from master to develop but I hope we don’t
end up in branch based split-brain where some folks
develop branch is created as of commit cc725e53e304781148a6bf077e05d844fe88207c
Please do not commit anything to master and use the respective branches.
Please go through the detailed wiki by Leo @
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git
~Rajani
On 05-Aug-2014, at 3:08 p
