Hi David,

> Please vote on the release candidate by Tuesday, 2012-09-11 15:00 PST

No from me.

I'd like to see the issue you introduced in the attached e-mail resolved
first.
I can probably do it on Wednesday, but feel free to make the change
yourself.

Regards,
Dies Koper

> -----Original Message-----
> From: David Lutterkort [mailto:[email protected]]
> Sent: Saturday, 8 September 2012 9:45 AM
> To: [email protected]
> Subject: [VOTE] release deltacloud 1.0.3, rc1
> 
> Hi all,
> 
> I am pleased to announce the RC1 for Deltacloud 1.0.3. The rc is at
> http://people.apache.org/~lutter/deltacloud/1.0.3/rc1/
> 
> Please vote on the release candidate by Tuesday, 2012-09-11 15:00 PST
> 
> KEYS: http://www.apache.org/dist/deltacloud/KEYS
> git tag: release-1.0.3-rc1
> git repo: git://github.com/apache/deltacloud.git or
>           https://git-wip-us.apache.org/repos/asf/deltacloud.git
> 
> This is a bugfix release. Highlights of the changes in this release:
>   * change the format of ~/.deltacloud/config: keys are now strings,
not
>     symbols - requires manual fixup
>   * server: remove extraneous quotes around ETag header value
>   * Drivers
>     + EC2
>       - list subnets in a VPC as realms
>       - allow launching of instances into a subnet in a VPC by
specifying
>         the corresponding subnet realm
>     + OpenStack
>       - pass server ID as string (JIRA 306)
>       - require openstack gem >= 1.0.4
>     + RHEV-M
>       - allow force stop of instance (JIRA 308)
>   * CIMI frontend:
>     - update handling of collections
>     - add disks and machine_volumes subcollections to Machine
>   * EC2 frontend: mount at ec2/ instead of /, i.e. you need to go to
>     http://localhost:3001/ec2 to use the frontend
> 
> For a full list of all changes see the NEWS file[1]
> 
> David
> 
> [1] https://github.com/apache/deltacloud/blob/master/NEWS (once the
> mirror updates)
> 
> 
> 
> 
> 
> 

--- Begin Message ---
Hi David,

Sure, go ahead. Documentation will need to be updated as well.

Regards,
Dies Koper

> -----Original Message-----
> From: David Lutterkort [mailto:[email protected]]
> Sent: Saturday, 25 August 2012 4:51 AM
> To: [email protected]
> Subject: Re: tests/config.yaml and $HOME/.deltacloud/config
> 
> On Fri, 2012-08-24 at 11:47 -0700, David Lutterkort wrote:
> > Hi,
> >
> > it was always my intention that you could use these two files
> > interchangeably - and that almost works; except that
tests/config.yaml
> > uses string keys, and ~/.deltacloud/config uses symbols as keys.
> >
> > That's easy enough to fix; I am just not sure which way around is
> > better. Is anybody besides me using ~/.deltacloud/config (by running
> > 'deltacloudd -c') ? Turning that into a file with string keys would
> > probably be the nicer solution.
> 
> I also just noticed that the FGCP driver is using
> ~/.deltacloud/config/fgcp - that obviously isn't going to work if
> ~/.deltacloud/config is a file. Could that be moved to
> ~/.deltacloud/drivers/fgcp ?
> 
> David
> 
> 




--- End Message ---

Reply via email to