Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: error (athena.apache.org: local policy)
Date: Thu, 12 Sep 2013 15:51:17 -0400
From: Chip Childers <chip.childers@sungard.com>
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Gearing up for an official CloudMonkey independent
 release
Message-ID: <20130912195117.GE3018@USLT-205755.sungardas.corp>
References: <20130826172743.GT50048@USLT-205755.sungardas.corp>
 <CANLSSBWiPnhQACaFxYDXLKAGbAJsP7PVooJgnj6etKGpfspG_w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CANLSSBWiPnhQACaFxYDXLKAGbAJsP7PVooJgnj6etKGpfspG_w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Tue, Aug 27, 2013 at 01:42:04PM +0530, Rohit Yadav wrote:
> On Mon, Aug 26, 2013 at 10:57 PM, Chip Childers
> <chip.childers@sungard.com> wrote:
> > Hi all,
> >
> > I'm looking at what it's going to take to get CloudMonkey out as an
> > official release.
> 
> Thanks Chip for taking this further.
> 
> >  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)
> 
> I don't see any NOTICE file in tree?
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=tree

pushing helps.  done

> 
> >
> > 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.
> 
> +1 I thought about doing it, but then decided not to within the repo
> but all existing cloudmonkey releases on pypi have the precache
> bundled with them, there is a build step in the Makefile which does
> that.

The problem I have with that is that I require a target CS mgmt server
to do the build.  I'd like to be able to allow anyone to build, and then
use, even if they don't have a version of CloudStack running that
supports API discovery.  Think about all of the 3.x or 4.0 users, and
CloudMonkey works (sort of) well enough for them.

> 
> >
> > 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?
> 
> Regards.
> 
> >
> > -chip
>