Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Received-SPF: pass (athena.apache.org: domain of lutter@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <1347303097.2740.38.camel@avon.watzmann.net>
Subject: RE: [VOTE] release deltacloud 1.0.3, rc1
From: David Lutterkort <lutter@redhat.com>
To: dev@deltacloud.apache.org
Date: Mon, 10 Sep 2012 11:51:37 -0700
In-Reply-To: <434A0ECB689CAF49A3A2321F30F2AB832271ACBB@FALEX03.au.fjanz.com>
References: <1347061495.2740.28.camel@avon.watzmann.net>
	 <434A0ECB689CAF49A3A2321F30F2AB832271ACB6@FALEX03.au.fjanz.com>
	 <434A0ECB689CAF49A3A2321F30F2AB832271ACBB@FALEX03.au.fjanz.com>
Organization: Red Hat Inc
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0

Hi Dies,

first off, the ~/.deltacloud/config file is nothing new - it's been
possible to use that for at least a year. If that hasn't caused trouble
yet, the changes in 1.0.3 won't cause trouble either.

The file is really only meant for developers to make it easier to use a
fixed set of credentials for dev, and for testing (if you pass --config
to deltacloudd, it reads credentials from that file) It can also be used
to pass credentials to tests. Though either way, it is possible to point
deltacloudd and the tests at a file in a different location.

In light of all that, are you ok with releasing 1.0.3 ?

David

On Sun, 2012-09-09 at 09:50 +1000, Koper, Dies wrote:
> HI David,
> 
> Unless of course this file is only used in tests, in that case Yes from
> me.
> 
> Regards,
> Dies Koper
> 
> 
> > -----Original Message-----
> > From: Koper, Dies [mailto:diesk@fast.au.fujitsu.com]
> > Sent: Sunday, 9 September 2012 9:32 AM
> > To: dev@deltacloud.apache.org
> > Subject: RE: [VOTE] release deltacloud 1.0.3, rc1
> > 
> > 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:lutter@redhat.com]
> > > Sent: Saturday, 8 September 2012 9:45 AM
> > > To: dev@deltacloud.apache.org
> > > 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)
> > >
> > >
> > >
> > >
> > >
> > >
> 
>