@cloudstack.apache.org
Cc: Donal Lafferty; Rajesh Battala; Anshul Gangwar
Subject: Re: [Merge] hyperv branch to master
+1
When you merge you will get a conflict in the spring configuration.
componentContext.xml and others are gone now in master. You will need to
update to the new style. The easiest will be to refer
Lafferty; Rajesh Battala; Anshul Gangwar
Subject: Re: [Merge] hyperv branch to master
+1
When you merge you will get a conflict in the spring configuration.
componentContext.xml and others are gone now in master. You will need to
update to the new style. The easiest will be to refer to XenServer
+1
On 10/28/13 4:41 AM, Devdeep Singh devdeep.si...@citrix.com wrote:
Hi,
I would like to merge the support for Hyperv to the master branch.
Development for this has been done by Donal, Rajesh, Anshul and I on
branch [1]. The feature was proposed for merge earlier [3] but unit tests
for hyperv
+1
-Original Message-
From: Chiradeep Vittal
Sent: 29 October 2013 06:43
To: dev@cloudstack.apache.org
Cc: Donal Lafferty; Rajesh Battala; Anshul Gangwar
Subject: Re: [Merge] hyperv branch to master
+1
On 10/28/13 4:41 AM, Devdeep Singh devdeep.si...@citrix.com wrote:
Hi
+1.
Thanks
Rajesh Battala
-Original Message-
From: Devdeep Singh
Sent: Monday, October 28, 2013 5:11 PM
To: dev@cloudstack.apache.org
Cc: Donal Lafferty; Rajesh Battala; Anshul Gangwar
Subject: [Merge] hyperv branch to master
Hi,
I would like to merge the support for Hyperv
On Mon, Oct 28, 2013 at 7:41 AM, Devdeep Singh devdeep.si...@citrix.com wrote:
Hi,
I would like to merge the support for Hyperv to the master branch.
Development for this has been done by Donal, Rajesh, Anshul and I on branch
[1]. The feature was proposed for merge earlier [3] but unit
+1
When you merge you will get a conflict in the spring configuration.
componentContext.xml and others are gone now in master. You will need
to update to the new style. The easiest will be to refer to XenServer
spring config for an example of how to do it. You can largely copy
and paste the
That could be a decision to put off for later.
The release process deals with single repos for now.
The signing will come up during the build right? How do other OSS C#
projects deal with it?
Perhaps they release binaries in addition to source?
On 10/29/13 9:35 AM, David Nalley da...@gnsa.us
Well - other projects within the ASF are finding a need to 'sign'
their convenience binaries, and folks are exploring those options now
to find something workable.
Why put it off? Creating a repo takes 5 minutes. IF putting it in its
own repo and adjusting our release processes is the right thing
: 29 October 2013 17:37
To: dev@cloudstack.apache.org
Cc: Donal Lafferty; Rajesh Battala; Anshul Gangwar
Subject: Re: [Merge] hyperv branch to master
Well - other projects within the ASF are finding a need to 'sign'
their convenience binaries, and folks are exploring those options now to find
easier to create a Master than to merge with Master :)
DL
-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: 29 October 2013 17:37
To: dev@cloudstack.apache.org
Cc: Donal Lafferty; Rajesh Battala; Anshul Gangwar
Subject: Re: [Merge] hyperv branch to master
Well
Hi,
I would like to merge the support for Hyperv to the master branch. Development
for this has been done by Donal, Rajesh, Anshul and I on branch [1]. The
feature was proposed for merge earlier [3] but unit tests for hyperv agent code
were requested [4].
Checklist:
The development for the
12 matches
Mail list logo
