Actually, never mind. We have committed multiple fixes and improvements in the last few days so imo it makes sense to skip 0.5.1 all-together and just go straight to 0.5.2 which includes all the recent changes.
I will try to prepare a 0.5.2 release tarball and start the voting process today. 2011/6/28 Tomaž Muraus <[email protected]> > OK, since everyone was busy and no-one voted I will restart voting today > and hopefully people will have time to test the release and cast their > votes. > > > 2011/6/18 Tomaž Muraus <[email protected]> > >> Test tarballs can be found at http://people.apache.org/~tomaz/libcloud/ >> >> This relase primary fixes two bugs which were introduced in 0.5.0: >> >> - Bug in deploy_node (deploy_node always threw an exception even if >> deployment was successful) >> - Bug in create_node in Nimbus driver (create_node threw an exception, >> because Nimbus doesn't support ex_create_tag functionality) >> >> Full changelog: >> >> *) Compute: >> - Fix deploy_node functionality and make it more robust >> >> *) Add new libcloud.compute drivers for: >> - SkaliCloud (skalicloud.com) >> - ServerLove (serverlove.com) >> >> *) Users can now pass file like objects to ScriptDeployment and >> SSHKeyDeployment constructor. >> >> *) Amazon EC2 driver: >> - Include node tags when calling list_nodes() >> [Trevor Pounds] >> >> *) Rackspace driver: >> - Properly handle response errors and only throw InvalidCredsError >> if >> the returned status code is 401 >> [Brad Morgan] >> >> *) Nimbus driver: >> - Fix the create_node method and make the "ex_create_tag" method a >> no-op, >> because Nimbus doesn't support creating tags. >> >> Note: >> >> To run the tests you now also need a "mock" library which is currently not >> installed by setup.py (need to figure out a good way to install dev >> dependencies such as coverage and mock). >> >> Please test the release and post your votes. >> >> +/- 1 >> [ ] Release Apache Libcloud 0.5.1 >> >> Vote closes on Tuesday June 21, 2011 at 10:00 CEST. >> >> Thanks, >> Tomaz >> > >
