cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prasanna Santhanam <>
Subject Re: [DISCUSS] Gearing up for an official CloudMonkey independent release
Date Tue, 27 Aug 2013 04:47:58 GMT
On Mon, Aug 26, 2013 at 01:27:43PM -0400, Chip Childers wrote:
> Hi all,
> I'm looking at what it's going to take to get CloudMonkey out as an
> official release.  Here's what I believe needs to be done:
> 1) Legal doc check (I think we're good here, since I just added the
> NOTICE file)
> 2) Release process document
> 3) Add an initial pre-cache file to the repo itself.  I want to do this,
> so that it doesn't require you to have a running 4.1+ ACS install in
> order to do a CloudMonkey build.
> 4) Kick out a release
> 5) Update the website to provide links to the
> cloudmonkey component's source repo and distinct artifacts.
> Once we get this first release out, we need to probably stop publishing
> to pypi outside of the *official release* process.  That being said,
> it'll be easier to release CloudMonkey independently.

Two questions:

If I read that correctly. It should still go to pypi but alongside CS

Seeing as Rohit wanted to do faster iterations [1] on CloudMonkey do you
want to make the CloudMonkey release process also an official process
but seperate from the ACS releases?

If yes to both, I'm +1 on the proposal. 


> Thoughts, comments, flames?
> -chip


Powered by

View raw message