In a release early and often fashion, 0.13 has been released just 2 months and 4 days after releasing the 0.12 final release and just 6 days after the 0.12.2 release. There have been 3 major focuses for this version: 1 - Support for the W3C automotive business group vehicle and data specs 2 - Documentation improvements 3 - Tool improvements. AMB support for the W3C auto-bg vehicle and data specs started in 0.12. 0.13 has additional API support: set(), availability() as well as data type support for the data spec[1]. Another related change is that the crosswalk plugin has moved into the AMB source tree (see xwalk/). I hope to do a blog sometime in the future about testing and developing with the vehicle web API. Stay tuned! Documentation has also greatly improved. We've added bluemonkey docs, documented the websocket protocol, and enhanced the library and DBus documentation. Check out the new docs here: http://otcshare.github.io/automotive-message-broker/0.13/html/index.html AMB 0.13 adds a new tool for amb testing and development: ambctl. This tool replaces amb-get, amb-set, amb-listen, and amb-get-history. Blog about this new tool here: https://01.org/automotive-message-broker/blogs/tripzero/2014/introducing-... For a more comprehensive list of AMB changes, check out the release notes: https://github.com/otcshare/automotive-message-broker/blob/0.13/RELEASE.md What's next? 0.14 already has some pretty cool features: more ambctl and documentation improvements, better plugin handling (plugins.d support), xwalk vehicle extension now supports all data that AMB does, and new DBus export capabilities. [1] - Support for all non-controversial data elements. What is supported is documented in the AMB DBus docs.