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 cloudstack.apache.org 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.

Thoughts, comments, flames?

-chip

Reply via email to