Changelog squashed.
CCing Kenton RE: the SONAME suggestion.
I suspect that because capnproto is relatively young the frequent SONAME breakages might be warranted -- I'm happy to work with that for now so long as it's not in breach of the DPM, though I agree this may be an issue for reverse dependencies.
Kenton, not sure how much you've had to deal with this in the past -- any thoughts here? Relevant docs:
"The SONAME and binary package name need not, and indeed normally should not, change if new interfaces are added but none are removed or changed, since this will not break binaries linked against the old shared library. Correct versioning of dependencies on the newer shared library by binaries that use the new interfaces is handled via the symbols or shlibs system."
This is complicated by the use of C++, which would place restrictions on things like virtual functions being added & removed. The KDE guys have documented some of this stuff: