diff --git a/CHANGES.rst b/CHANGES.rst
index 586c4e9..09d8240 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -1,15 +1,38 @@
 Changes in the development version
 ==================================
 
+No changes.
+
+
+Changes in version 0.3.0
+========================
+
+Backwards-incompatible changes
+------------------------------
+
+* Nodes have now an ``id`` field, matching the VirtualBox UUID.
+  You must recreate all the nodes defined in your ``~/.libcloud-vagrant``
+  catalogue.
+
+
+Backwards-compatible changes
+----------------------------
+
 * New command-line tool ``libcloud-vagrant`` to do simple operations
   with Vagrant nodes created by Libcloud.
 
+* Interactions with Vagrant and Virtualbox are protected by a
+  filesystem-based lock.
+
 * Unit tests use now a free 24-bit network in the 192.168/16 range,
   instead of using hard-coded ones.
 
 * The host network interfaces of public networks are destroyed when the
   Vagrant network objects are destroyed.
 
+* ``libcloud-vagrant`` now makes fewer calls to the Virtualbox
+  ``VBoxManage`` command.
+
 
 Changes in version 0.2.0
 ========================
diff --git a/README.rst b/README.rst
index 9ea646e..034de5f 100644
--- a/README.rst
+++ b/README.rst
@@ -81,6 +81,12 @@ operations with Vagrant nodes created by Libcloud::
             environment.
     $
 
+``libcloud-vagrant`` is *not* thread- or multiprocess-safe. Interactions
+with Vagrant and with the Virtualbox command-line tools are protected
+with a filesystem-based lock, which (hopefully) serializes things, so
+even if they worked, concurrent operations would not give you much
+benefit.
+
 
 Requirements
 ------------
diff --git a/libcloudvagrant/__init__.py b/libcloudvagrant/__init__.py
index 96243cb..1199ea1 100644
--- a/libcloudvagrant/__init__.py
+++ b/libcloudvagrant/__init__.py
@@ -59,7 +59,7 @@
                                            "ca-bundle.crt"))
 
 
-__version__ = "0.2.0"
+__version__ = "0.3.0"
 
 
 def test():