My vote is +1 (non binding) I've executed the release verification script ./verify_jclouds_release.sh 1.7.3-rc1.available at https://wiki.apache.org/jclouds/Validate%20a%20Release
* Executed the validation script available at https://wiki.apache.org/jclouds/Validate%20a%20Release for linux: - Source code compiles and passes all tests - There are no RAT violations - Checksums match - Signatures match Please find also the results of the live tests I've run against SoftLayer CCI provider: Tests run: 151, Failures: 22, Errors: 0, Skipped: 11 Best, Andrea On Thu, May 29, 2014 at 9:21 AM, Shrinand Javadekar <[email protected]> wrote: > My vote is +1 (non binding) > > * I ran the verify_jclouds_release script and it completed > successfully. The logs from that can be found here: > http://on.magfs.io/1tlErFP > * I did a mvn clean install in the jclouds code and it completed > successfully. The logs from that are attached. > * I ran live blobstore tests against atmos, azure, aws-s3, > cloudfiles-us, hpcloud and swift. They all completed successfully. The > logs from these live tests are also attached. > > > > On Wed, May 28, 2014 at 9:14 AM, Ignasi Barrera <[email protected]> wrote: >> My vote is a +1 (binding). >> >> These is my release verification checklist: >> >> * Executed the validation script: >> - Source code compiles and passes all tests >> - There are no RAT violations >> - Checksums match >> - Signatures match >> * All LICENSE and NOTICE files are correct >> * Releaser key is also present in: >> https://people.apache.org/keys/group/jclouds.asc >> * Verified the staging repository by downloading the "jclouds-all" >> dependency. >> * Verified the CLI with the staging repository and by running commands >> that use the "digitalocean" feature >> * Live tests executed (test failures are here, one file for each >> provider: https://gist.github.com/nacx/9b351642921328119143): >> - elastichosts-lon-b: Tests run: 150, Failures: 0, Errors: 0, Skipped: 0 >> - digitalocean: Tests run: 56, Failures: 0, Errors: 0, Skipped: 0 >> - cloudsigma2-lvs: Tests run: 50, Failures: 0, Errors: 0, Skipped: 0 >> - chef: Tests run: 50, Failures: 0, Errors: 0, Skipped: 0 >> - enterprisechef: Tests run: 47, Failures: 0, Errors: 0, Skipped: 0 >> - aws-ec2: 194, Failures: 29, Errors: 0, Skipped: 13 >> - rackspace-cloudservers-us: Tests run: 145, Failures: 10, Errors: >> 0, Skipped: 0 >> - rackspace-cloudloadbalancers-us: Tests run: 9, Failures: 0, >> Errors: 0, Skipped: 0 >> - rackspace-clouddns-us: Tests run: 30, Failures: 0, Errors: 0, Skipped: 0 >> - rackspace-cloudblockstorage-us: Tests run: 7, Failures: 1, Errors: >> 0, Skipped: 5 >> - rackspace-cloudfiles-us: Tests run: 53, Failures: 2, Errors: 0, Skipped: >> 6 >> - rackspace-autoscale-us: Tests run: 23, Failures: 0, Errors: 0, Skipped: 0 >> >> Additional notes: >> >> * There are many build failures in was-ec2 we should address, but most >> were already present in previous versions, so I wouldn't stop 1.7.3 >> because of this. >> * The failures in rackspace-cloudservers-us are mostly due to template >> issues. I think it is a matter of changing the default template >> pattern (and should pretty straightforward to fix), but I'll leave >> that for the rackers :) >> * For some reason I've not been able to run the >> backspace-clouddatabases-us live tests. Could someone else run them? >> >> On 27 May 2014 22:49, Everett Toews <[email protected]> wrote: >>> +1 >>> >>> Verified RAT, build, tests, checksums and signatures >>> Ran Rackspace SmokeTest against the 1.7.3 staging repo >>> >>> Everett >>> >>> >>> On May 27, 2014, at 3:39 PM, Everett Toews <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> This is the first release candidate for Apache jclouds 1.7.3. >>>> >>>> Please use the separate [DISCUSS] thread for anything but votes. >>>> >>>> It fixes the following issues: >>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326750&styleName=Html&projectId=12314430 >>>> >>>> *** Please download, test and vote by Friday, May 30, 13:30 PDT / 15:30 >>>> CDT / 16:30 EDT >>>> >>>> Note that we are voting upon the source (tag), binaries are provided for >>>> convenience. >>>> >>>> Source and binary files: >>>> https://dist.apache.org/repos/dist/dev/jclouds/1.7.3-rc1/ >>>> >>>> Maven staging repo: >>>> https://repository.apache.org/content/repositories/orgapachejclouds-1018 >>>> >>>> The tags to be voted upon: >>>> >>>> - jclouds - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=tag;h=76f695501c2ed58cfba87340b51b0a6212e17c18 >>>> (SHA-1: 8e34e00dff4bd08f1eaa48fcdade0c9eef0b23bf) >>>> >>>> - jclouds-labs - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;a=tag;h=0ba36bf3c978d8ff919c85a3ef23bbd8ae004f1d >>>> (SHA-1: 76d262dfc8bec5405fe54baea4d60bbac2a2610b) >>>> >>>> - jclouds-labs-openstack - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-openstack.git;a=tag;h=7db3a66d4a5092498ce6b4bf24e79d41bace01f5 >>>> (SHA-1: bbf81ed770160c92f44b3c1634271d5751b6606e) >>>> >>>> - jclouds-labs-aws - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-aws.git;a=tag;h=b2f73944f144cd01f5fba947ce5d51066a13a190 >>>> (SHA-1: 2941d9c8a921b189c8b89409c97a07ba7e950809) >>>> >>>> - jclouds-labs-google - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-google.git;a=tag;h=b819321b784c678baf17a2f4b2397c32c12ee64b >>>> (SHA-1: 0f2be433e99a7daa88a25e3c967b920299b7d578) >>>> >>>> - jclouds-chef - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds-chef.git;a=tag;h=b943f4a0625c2bcebb75addabed47cb687186aff >>>> (SHA-1: 48a8f36a5deafb6d22e47da3ae0a517630842d44) >>>> >>>> - jclouds-karaf - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;a=tag;h=6f27cefe5c5dafae532347897336aa0effa44407 >>>> (SHA-1: 501515373b4bdd50de06e90214b7a827f6b76986) >>>> >>>> - jclouds-cli - >>>> https://git-wip-us.apache.org/repos/asf?p=jclouds-cli.git;a=tag;h=a67ff8b9a1b498192aa0ef651997875273d339f4 >>>> (SHA-1: 5aa134da52783d9f9e321cdf1d7622d4aebdeb9d) >>>> >>>> jclouds KEYS file containing PGP keys we use to sign the release: >>>> http://www.apache.org/dist/jclouds/KEYS >>>> >>>> [ ] +1 >>>> [ ] 0 >>>> [ ] -1 (explain why) >>>
