[RELEASE] branching and tagging the components

Crag Wolfe cwolfe at redhat.com
Mon Nov 26 19:24:01 UTC 2012


On 11/23/2012 01:22 PM, Giulio Fidente wrote:
> On 11/20/2012 05:28 PM, Hugh Brock wrote:
>> 1. Each separate upstream needs to be fully testable in isolation from
>> its dependencies -- i.e. fully mocked out. We have made some progress
>> towards this, I'm not sure if it's complete or not.
>
> I'm currently working on some functional testing for the imgfac REST
> interface; I'd like to see this merged at some point, meantime feedback
> is *very much* appreciated:
>
> https://github.com/giulivo/imagefactory-tests-restapi
>
>> 2. An upstream with dependencies needs to be integration tested against
>> known-good versions of its dependencies. It's probably a Release Cabal
>> function to decide what the "stable" versions of deps are and approve
>> revisions to those as part of release planning.
>
> back to the basics; I'm trying to get conductor installed via dev-tools
> on centos6 (and it's failing with and without rbenv because of bundler
> missing)
>
> what version of deltacloud and imagfactory should I provide it with?
> 'latest' stable from both?
>
For now, I do "yum install aeolus-all" on one host (as per 
http://www.aeolusproject.org/get_it.html) and point to it from another 
host where I run dev-tools.  So, that is a place to start and then one 
can always re-point the local conductor to another newer component if 
desired.




More information about the aeolus-devel mailing list