+1. All libraries of marvin and tests using them will now be at single place. Though marvin and tests under it are used to test cloudstack, segregating it from main cloudstack product code is good. Going ahead, few more changes will be required to make tests run automatically based upon the cloudstack release version on a given test bed, but that can be enhanced separately.
Regards, Santhosh ________________________________________ From: Sebastien Goasguen [run...@gmail.com] Sent: Wednesday, October 02, 2013 2:25 PM To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Breaking out Marvin from CloudStack +1 On Oct 2, 2013, at 1:58 PM, Edison Su <edison...@citrix.com> wrote: > Seems Marvin won't depend on commands.xml any more, thus won't depend on any > artifacts build from cloudstack. So I am +1. > >> -----Original Message----- >> From: Prasanna Santhanam [mailto:t...@apache.org] >> Sent: Wednesday, October 02, 2013 10:14 AM >> To: CloudStack Dev >> Subject: [DISCUSS] Breaking out Marvin from CloudStack >> >> I would like to seperate marvin from the main cloudstack repo. Much of >> marvin's development has little coupling with CloudStack. >> >> Similar to CloudMonkey, marvin undergoes rapid changes and it is essential >> to provide a smooth workflow and faster releases for those working with it. >> >> There are also a small set of people currently looking at marvin for testing >> right now. Often, their reviews and QA effort is mixed with those of >> cloudstack itself. By having a different repo I'd like to be able to provide >> commit access to those working on marvin alone quickly to help with testing. >> >> After separating marvin >> 0. we will have a separate release cycle for marvin 1. we will have a new >> home for marvin's docs using Sphinx 2. if possible, a different criteria for >> providing commit access to marvin's repos. >> 3. all tests of cloudstack will also move to marvin's repository >> >> Thoughts? >> >> -- >> Prasanna., >> >> ------------------------ >> Powered by BigRock.com >
