[libvirt] ANNOUNCE: ruby-libvirt bindings 0.3.0

[Chris Lalancette]

All,
     I'm pleased to announce the release of 0.3.0 of the ruby-libvirt bindings.
This release has a number of updates:

 * Implementation of Libvirt::open_auth, Libvirt::event_register_impl
 * Updated Connect class, implementing conn.compare_cpu, conn.baseline_cpu,
   conn.domain_event_register_any, conn.domain_event_deregister_any,
   conn.domain_event_register, conn.domain_event_deregister, and
   conn.create_domain_xml.
 * Updated Domain class, implementing dom.get_vcpus, dom.update_device,
   dom.scheduler_type, dom.scheduler_parameters, dom.scheduler_parameters=,
   dom.num_vcpus, dom.vcpus_flags=, and dom.qemu_monitor_command.
 * Updated Interface class, implementing interface.free
 * Many potential memory leaks have been fixed.
 * Many bugfixes.
 * Documentation update of many methods, including all of the lookup methods
   that were missing before.

With the above list, almost all of the APIs up to and including libvirt 0.8.6
are covered.  There are a few that I have not yet had time to implement; you
can look at the list in the README file in the source tree to see which ones
are missing.

The tarballs and source RPMs are here: http://libvirt.org/ruby/download/
The git repository is here: http://libvirt.org/git/?p=ruby-libvirt.git;a=summary
The documentation for all of the APIs are here: http://libvirt.org/ruby/api/index.html
I've uploaded some examples on how to use the bindings:
http://libvirt.org/ruby/documentation.html
I've also pushed a new gem to rubygems.org; you should be able to use
'gem install ruby-libvirt' (if you haven't installed them before) or
'gem update ruby-libvirt' (if you have them installed already).

If you have time, and are interested in the bindings, please give these new
ones a whirl and let me know if they work for you.  Note that release 0.3.0
is intended to be fully backwards compatible with release 0.2.0 and 0.1.0.
If you find that they are not, or find any other problems with the ruby
bindings, please report it to the libvirt development mailing list
(and CC me) so that I can take a look at them.

Thanks,
-- 
Chris Lalancette