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.apache.org/repos/asf?p=couchdb-admin.git
Actually, perhaps we do. We currently have some "release tooling" sitting in tools/build within the main repo. Time to break that out? The tool I published on github, although the example is for CloudStack, was meant to be a thing that different projects can use. I realize that it's not much more than what a shell script can do, but I found it useful to get a clear picture of what steps work vs fail. > > On 23 April 2013 14:36, Chip Childers <chip.child...@sungard.com> 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 you manually work with the release, > > however many of the up-front steps are easily scripted. I put together > > a generic framework for defining and running a set of release > > verification instructions yesterday, including the definition of the > > CloudStack release verification steps as the example configuration [2]. > > > > Feel free to use it if you think it would help you (especially the RM's > > that may have to re-spin an RC over and over to ensure that it's right). > > > > -chip > > > > [1] > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure > > > > [2] https://github.com/chipchilders/cloudstack-release-verification-tool > > > > > > -- > NS
