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
