Chip, that makes perfect sense to me. On 10/2/13 1:10 PM, "Chip Childers" <chipchild...@apache.org> wrote:
>On Wed, Oct 02, 2013 at 07:38:33PM +0000, Alex Huang wrote: >> I don't really understand what purpose would this serve. Would we ever >>use newer marvin against older CloudStack or vice versa? What's the >>benefit? >> >> I can understand it for cloudmonkey because cloudmonkey is an admin cli >>tool and reving it differently is not a bad idea. I just don't see it >>for marvin and, especially for the tests. >> >> --Alex > >IMO, we should consider Marvin the "framework" to be the thing to break >out, and the tests should be different from the framework. > >Now that leads to the question: to test or not to test (in the main >repo)? > >I'd suggest that *tests* belong in the main repo, because they are tied >to the software's capabilities and versions. > >The Marvin framework, on the other hand, since the re-work that Prasanna >did, is mostly distinct (and uses API discovery). > >Anyone else agree?
