Releases

From 714532355f00bae2b820d53f5299e258b5078afd Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Tue, 28 Feb 2006 14:22:33 +0000 Subject: [PATCH] * NEWS configure.in libvirt.spec.in include/libvirt.h docs/*: preparing release 0.0.6 Daniel --- ChangeLog | 5 +++++ NEWS | 8 ++++++++ configure.in | 2 +- docs/errors.html | 4 ++-- docs/libvir.html | 13 +++++++++++-- docs/news.html | 7 ++++++- include/libvirt.h | 2 +- include/libvirt/libvirt.h | 2 +- libvirt.spec.in | 6 ++++++ python/Makefile.am | 3 ++- 10 files changed, 43 insertions(+), 9 deletions(-) diff --git a/ChangeLog b/ChangeLog index c4901b2e9c..79a7845ea6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Tue Feb 28 15:21:48 CET 2006 Daniel Veillard + + * NEWS configure.in libvirt.spec.in include/libvirt.h docs/*: + preparing release 0.0.6 + Tue Feb 28 14:57:25 CET 2006 Daniel Veillard * docs/errors.html docs/libvir.html docs/*: added a page about diff --git a/NEWS b/NEWS index f8dbd1f2b4..51b1204ef5 100644 --- a/NEWS +++ b/NEWS @@ -5,6 +5,14 @@ http://libvirt.org/news.html Releases +0.0.6: Feb 28 2006: + - add UUID lookup and extract API + - add error handling APIs both synchronous and asynchronous + - added minimal hook for error handling at the python level, improved the + python bindings + - augment the documentation and tests to cover error handling + + 0.0.5: Feb 23 2006: - Added XML description parsing, dependance to libxml2, implemented the creation API virDomainCreateLinux() diff --git a/configure.in b/configure.in index ccfd6e1019..375164703d 100644 --- a/configure.in +++ b/configure.in @@ -5,7 +5,7 @@ AC_CANONICAL_HOST LIBVIRT_MAJOR_VERSION=0 LIBVIRT_MINOR_VERSION=0 -LIBVIRT_MICRO_VERSION=5 +LIBVIRT_MICRO_VERSION=6 LIBVIRT_MICRO_VERSION_SUFFIX= LIBVIRT_VERSION=$LIBVIRT_MAJOR_VERSION.$LIBVIRT_MINOR_VERSION.$LIBVIRT_MICRO_VERSION$LIBVIRT_MICRO_VERSION_SUFFIX LIBVIRT_VERSION_INFO=`expr $LIBVIRT_MAJOR_VERSION + $LIBVIRT_MINOR_VERSION`:$LIBVIRT_MICRO_VERSION:$LIBVIRT_MINOR_VERSION diff --git a/docs/errors.html b/docs/errors.html index 00f7499475..d1a1b8d7a5 100644 --- a/docs/errors.html +++ b/docs/errors.html @@ -33,13 +33,13 @@ set specifically to a connection with

So error handling in the code is the

In all cases the error informations are provided as a virErrorPtr pointer to read-only structure virError containing the -following fields:

code: an error number from the virErrorNumber +following fields:
- code: an error number from the virErrorNumber enum
- domain: an enum indicating which part of libvirt raised the error see virErrorDomain
- level: the error level, usually VIR_ERR_ERROR, though there is room for warnings like VIR_ERR_WARNING
- message: the full human-readable formatted string of the error
- message: the full human-readable formatted string of the error
- conn: if available a pointer to the virConnectPtr connection to the hypervisor where this happened
- dom: if available a pointer to the virDomainPtr domain diff --git a/docs/libvir.html b/docs/libvir.html index d54ea6be24..34c767bad6 100644 --- a/docs/libvir.html +++ b/docs/libvir.html @@ -33,6 +33,15 @@ development of libvirt, it is preferable when possible to just use the CVS version or snapshot, contact the mailing list and check the ChangeLog to gauge progresses.
  +
  0.0.6: Feb 28 2006
  +
  - add UUID lookup and extract API
  - add error handling APIs both synchronous and asynchronous
  - added minimal hook for error handling at the python level, improved the + python bindings
  - augment the documentation and tests to cover error handling
  +
  0.0.5: Feb 23 2006
  - Added XML description parsing, dependance to libxml2, implemented the @@ -417,7 +426,7 @@ set specifically to a connection with
    href="html/libvirt-virterror.html#virErrorPtr">virErrorPtr pointer to read-only structure virError containing the -following fields:
    +following fields:
    - code: an error number from the virErrorNumber @@ -427,7 +436,7 @@ following fields:
      href="html/libvirt-virterror.html#virErrorDomain">virErrorDomain
    - level: the error level, usually VIR_ERR_ERROR, though there is room for warnings like VIR_ERR_WARNING
    - message: the full human-readable formatted string of the error
    - message: the full human-readable formatted string of the error
    - conn: if available a pointer to the virConnectPtr connection to the hypervisor where this happened