Currently we are running automation cloudstack repo , please don't remove marvin from cloudstack unless new repo is working seamlessly.
In new marvin specific repo there will be same branch similar to cloudstack repo branches ? Regards, Rayees -----Original Message----- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Wednesday, October 02, 2013 11:25 AM To: dev@cloudstack.apache.org Subject: Re: [MERGE] marvin-refactor to master On Oct 2, 2013, at 12:56 PM, Prasanna Santhanam <t...@apache.org> wrote: > On Wed, Oct 02, 2013 at 12:51:18PM -0400, Chip Childers wrote: >> On Wed, Oct 02, 2013 at 10:12:40PM +0530, Prasanna Santhanam wrote: >>> I've also tried to disconnect marvin from depending on CloudStack's >>> build and repo. This will help split marvin from CloudStack which I >>> will discuss in a seperate thread. >> >> Should we just use this branch as the source for a new repo, and move >> on from there? > > I haven't fully disconnected it but will start a DISCUSS thread if > there are any concerns about splitting it from the existing repo. If > there is consensus we can break it apart from the branch. > > -- > Prasanna., > I would probably break it and merge in the separate project, that would make a clean cut. +1 > ------------------------ > Powered by BigRock.com >
