I've executed the release verification script and everything is ok: * Build passes with no tests failed and no RAT violations * Signatures match * Checksums match
LICENSE and NOTICE files are correct in all projects. I've also executed the live tests for the following providers: * cloudsigma2-lvs - Tests run: 50, Failures: 0, Errors: 0, Skipped: 0 * digitalocean: Tests run: 53, Failures: 0, Errors: 0, Skipped: 0 * enterprisechef: Tests run: 47, Failures: 0, Errors: 0, Skipped: 0 * chef11: Tests run: 50, Failures: 0, Errors: 0, Skipped: 0 * chef10: Tests run: 50, Failures: 1, Errors: 0, Skipped: 2 Failed tests: testListCookbooks(org.jclouds.chef.ChefApiLiveTest): There are no versions of the cookbook: jcloudstest-nacx expected:<false> but was:<true> The failed test in chef10 seems to be related to a corrupted cookbook I have in the server, so I'm not worried about it. I've also tested Joyentcloud, and the provider is broken (and I'm sure it has been broken for many releases). The API seems to have changed and some objects in the domain model no longer match the objects returned by the API. A general review of the provider should be done, or we could consider deprecating/removing it. It is also using the v6.5 API and Basic Auth when their v7 api has been out there for a reasonable time now. There is also a better authentication method based on user's SSH keys. Anyway, it is in labs and I think it shouldn't stop the release. It is not usable right now and if someone was using it, we would have seen some emails in the mailing lists. The release looks OK for me, but I'd wait to give my +1 until I am able to test the Guava/JVM issue tomorrow. On 6 February 2014 16:32, Ignasi Barrera <[email protected]> wrote: > This thread is for discussion of the first release candidate for > Apache jclouds-1.7.1. Please use this thread for discussion of issues > uncovered in the RC, questions you may have about the RC, etc. Thank > you.
