Hi David, I can assure you that if we knew of a reason to breakup our plugins into separate repos, it would have been brought up weeks ago.
It is far, far 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 - 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 to do, I'd rather do it > now than later. If it isn't the right thing to do, then staying put is fine > as well. > > --David > > On Tue, Oct 29, 2013 at 1:29 PM, Chiradeep Vittal > <chiradeep.vit...@citrix.com> wrote: > > 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> wrote: > > > >>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 > >>>tests for hyperv agent code were requested [4]. > >>> > >> > >>I know this has been discussed several times, but what was the > >>decision about making the agent code live in its own repo? > >>It's C#, might need to be signed to actually run easily on Windows, etc. > >> > >>--David > >
