~Rajani


On 05-Aug-2014, at 4:15 pm, Rohit Yadav <rohit.ya...@shapeblue.com> wrote:

> Hi Rajani,
> 
> On 05-Aug-2014, at 12:35 pm, Rajani Karuturi <rajani.karut...@citrix.com> 
> wrote:
> 
>> The switch to the new git flow is postponed to 7th aug.
> 
> Thanks for that, this means you’ll do it again on 7th August 00:00UTC?

I am planning to do this 48 hrs from now, which would be around 5:00PM IST on 
7th august.

> 
> Meanwhile this means we’re to follow our normal workflow and commit on master.
> 
>> we have two open questions to answer before that:
>> 1. Can we enable a git hook to prevent the commits to master post the switch?
> 
> It’s possible theoretically but to do that in less than 48 hours could be a 
> challenge, you can open a ticket on JIRA/ASF-infra or contact the fine folks 
> on ASF infra such as humbledooh (irc etc.).
> 
>> 2. should we create the release branch as well or wait for RM to do it?
> 
> Since, you’re implementing the gitflow worflow, you should do it (create all 
> the necessary branches).
> 
> Regards.
> 
>> 
>> 
>> ~Rajani
>> 
>> 
>> 
>> On 05-Aug-2014, at 3:16 pm, Rajani Karuturi 
>> <rajani.karut...@citrix.com<mailto:rajani.karut...@citrix.com>> wrote:
>> 
>> Hi Daan,
>> 
>> I created develop branch on commit cc725e53e304781148a6bf077e05d844fe88207c 
>> and pushed it.
>> 
>> 
>> I am trying to create the  4.5 branch. For this, I need to change the 
>> version number in develop branch.
>> Release Procedure wiki mention a script to change to version number. [1]
>> Is it safe to just run it?
>> 
>> Should we wait for 4.5 RM to create the release the branch?
>> 
>> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
>> 
>> 
>> 
>> 
>> ~Rajani
>> 
>> 
>> 
>> On 05-Aug-2014, at 2:27 pm, Daan Hoogland 
>> <daan.hoogl...@gmail.com<mailto:daan.hoogl...@gmail.com>> wrote:
>> 
>> On Tue, Aug 5, 2014 at 10:52 AM, Rajani Karuturi
>> <rajani.karut...@citrix.com<mailto:rajani.karut...@citrix.com>> wrote:
>> Daan,
>> I think we should do the branch related changes[1] and make the switch. Are 
>> we waiting for a RM for 4.5?
>> 
>> [1] 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git#Git-Movetogit-flow
>> 
>> 
>> ~Rajani
>> 
>> 
>> No Rajani, We don't need an RM to make the switch (as Leo pointed
>> out). Yours the honor as you came up with the idea. Let's go for it.
>> I'll model the 4.4 work as much as possible towards your example.
>> 
>> --
>> Daan
>> 
>> 
> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +41 779015219 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
> CloudStack Infrastructure 
> Support<http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training 
> Courses<http://shapeblue.com/cloudstack-training/>
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

Reply via email to