Re: Release Verification Tool - if you're interested

2013-05-06 Thread Chip Childers
On Sat, May 04, 2013 at 01:33:38PM +0100, Noah Slater wrote: > Wow. This is a great idea! > > On CouchDB we have couchdb-admin.git and we keep stuff like this in that > repos. Might we want to consider something similar? (We also use it to keep > email templates in, etc.) > > https://git-wip-us.a

Re: Release Verification Tool - if you're interested

2013-05-04 Thread Noah Slater
Wow. This is a great idea! On CouchDB we have couchdb-admin.git and we keep stuff like this in that repos. Might we want to consider something similar? (We also use it to keep email templates in, etc.) https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git On 23 April 2013 14:36, Chip Child

Re: Release Verification Tool - if you're interested

2013-04-23 Thread John Burwell
Chip, Worked like a charm within 15 minutes -- just now getting around to ack'ing the success. Thanks, -John On Apr 23, 2013, at 11:57 AM, Chip Childers wrote: > On Tue, Apr 23, 2013 at 11:51:02AM -0400, John Burwell wrote: >> root@zone1:/tmp/cloudstack# gpg --verify >> apache-cloudstack-4.1

Re: Release Verification Tool - if you're interested

2013-04-23 Thread Chip Childers
On Tue, Apr 23, 2013 at 11:51:02AM -0400, John Burwell wrote: > root@zone1:/tmp/cloudstack# gpg --verify > apache-cloudstack-4.1.0-src.tar.bz2.asc > gpg: Signature made Mon 22 Apr 2013 04:45:37 PM PDT using RSA key ID A99A5D58 > gpg: Can't check signature: public key not found > > What am I doing

Re: Release Verification Tool - if you're interested

2013-04-23 Thread John Burwell
Chip, I just attempted to use the release verification script on Ubuntu 12.04.2 LTS with the stock instructions.conf file provided in the git repo, and I receiving the following error: root@zone1:/opt/release-verification-tool# ./verify-release.py -i instructions.conf -v 4.1.0 -c 7048baaa44178

Re: Release Verification Tool - if you're interested

2013-04-23 Thread Chip Childers
On Tue, Apr 23, 2013 at 9:36 AM, Chip Childers wrote: > Hi all, > > Going through the process of validating the RC's (and several validation > rounds before announcing an RC), I got tired of manually following the > steps in our release testing process [1]. > > Some of the steps do require that yo