Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-11 Thread Rohit Yadav
day 10 December 2014 10:17 PM, Suresh Sadhu wrote: +1 -Original Message- From: Rajani Karuturi [mailto:raj...@apache.org] Sent: 10 December 2014 06:20 To: dev@cloudstack.apache.org Subject: Re: [VOTE] Simplify CloudMonkey's branching/maintenance process +1 On Tue, Dec 9, 2014 at 1

RE: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-10 Thread Suresh Sadhu
+1 -Original Message- From: Rajani Karuturi [mailto:raj...@apache.org] Sent: 10 December 2014 06:20 To: dev@cloudstack.apache.org Subject: Re: [VOTE] Simplify CloudMonkey's branching/maintenance process +1 On Tue, Dec 9, 2014 at 18:55 PM, Rohit Yadav wrote: Hi, CloudMonkey&

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-10 Thread Erik Weber
On tir. 9. des. 2014 at 14.27 Rohit Yadav wrote: > Hi, > > CloudMonkey's git repo history is mostly linear and the work on master > is simply getting synced on 5.3 branch. I want to ask the community if > anyone has any objections on just keeping master as the working branch > and have branches w

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Abhinandan Prateek
+1, keep it simple > On 10-Dec-2014, at 4:21 am, Daan Hoogland wrote: > > +1 , I wish we could make such a call on the stack. > > On Tue, Dec 9, 2014 at 7:14 PM, sebgoa wrote: >> >> On Dec 9, 2014, at 2:25 PM, Rohit Yadav wrote: >> >>> Hi, >>> >>> CloudMonkey's git repo history is mostly linea

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Mike Tutkowski
+1 On Tuesday, December 9, 2014, Rajani Karuturi wrote: > +1 > > > On Tue, Dec 9, 2014 at 18:55 PM, Rohit Yadav > > wrote: > > Hi, > > CloudMonkey's git repo history is mostly linear and the work on master > is simply getting synced on 5.3 branch. I want to ask the community if > anyone has any

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Rajani Karuturi
+1 On Tue, Dec 9, 2014 at 18:55 PM, Rohit Yadav wrote: Hi, CloudMonkey's git repo history is mostly linear and the work on master is simply getting synced on 5.3 branch. I want to ask the community if anyone has any objections on just keeping master as the working branch and have branches when

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Ian Duffy
+1, it makes sense for cloudmonkey :) On 9 December 2014 at 22:51, Daan Hoogland wrote: > +1 , I wish we could make such a call on the stack. > > On Tue, Dec 9, 2014 at 7:14 PM, sebgoa wrote: > > > > On Dec 9, 2014, at 2:25 PM, Rohit Yadav > wrote: > > > >> Hi, > >> > >> CloudMonkey's git repo

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Daan Hoogland
+1 , I wish we could make such a call on the stack. On Tue, Dec 9, 2014 at 7:14 PM, sebgoa wrote: > > On Dec 9, 2014, at 2:25 PM, Rohit Yadav wrote: > >> Hi, >> >> CloudMonkey's git repo history is mostly linear and the work on master >> is simply getting synced on 5.3 branch. I want to ask the

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread sebgoa
On Dec 9, 2014, at 2:25 PM, Rohit Yadav wrote: > Hi, > > CloudMonkey's git repo history is mostly linear and the work on master > is simply getting synced on 5.3 branch. I want to ask the community if > anyone has any objections on just keeping master as the working branch > and have branches w

RE: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Stephen Turner
+1 as long as CloudMonkey remains backwards compatible with older CloudStack releases, so that we don't have to preserve old monkeys to talk to old stacks. -- Stephen Turner -Original Message- From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] Sent: 09 December 2014 13:26 To: dev Su

Re: [VOTE] Simplify CloudMonkey's branching/maintenance process

2014-12-09 Thread Wido den Hollander
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/09/2014 02:25 PM, Rohit Yadav wrote: > Hi, > > CloudMonkey's git repo history is mostly linear and the work on > master is simply getting synced on 5.3 branch. I want to ask the > community if anyone has any objections on just keeping master a