I've cut the RC2 using the release script and it worked pretty well. The process was completely unattended and took around 3 hours. Take into account that it builds *all* repos twice (the release version and the next snapshot), and a third time, without running the tests, to generate the javadocs and upload all artifacts to the staging repo. This was on my laptop (MacBook Air), but with a better machine and a better Internet connection the release might take less time. In any case, it is a completely unattended proces, so... WIN!
I've executed the following live tests: aws-ec2: Tests run: 113, Failures: 7, Errors: 0, Skipped: 4 enterprisechef: Tests run: 20, Failures: 0, Errors: 0, Skipped: 0 digitalocean: Tests run: 57, Failures: 0, Errors: 0, Skipped: 0 cloudsigma2-lvs: Tests run: 78, Failures: 7, Errors: 0, Skipped: 10 google-compute-engine: Tests run: 153, Failures: 2, Errors: 0, Skipped: 9 hpcloud-compute: Tests run: 73, Failures: 2, Errors: 0, Skipped: 6 AWS presents the already known test failures, and other transient failures due to an Internet connection glitch that made some live tests fail. The failures in CloudSigma seem to be due to the image being used. It takes long until it boots completely and the compute service sun script tests are failing due to a timeout. HPCloud failures are the same ones than in the previous RC. Shouldn't be blocking, and the new tests that verify the issue found in RC1 are passing. On 24 March 2015 at 15:35, Ignasi Barrera <n...@apache.org> wrote: > This thread is for discussion of the second release candidate for > Apache jclouds 1.9.0. Please use this thread for discussion of issues > uncovered in the RC, questions you may have about the RC, etc. > > Thank you.
