Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Wed, 2 Oct 2013 22:44:27 +0530
From: Prasanna Santhanam <tsp@apache.org>
To: CloudStack Dev <dev@cloudstack.apache.org>
Subject: [DISCUSS] Breaking out Marvin from CloudStack
Message-ID: <20131002171427.GA21916@cloud-2.local>
Mail-Followup-To: CloudStack Dev <dev@cloudstack.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)

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