Some thoughts about Mercurial bookmarks

[Jensen, Aaron]

> I agree and have plans to fix this, but it is a big backwards-compatibility breaking 
> change that the community will need to noodle over for a bit most likely. I have 
> a series of changes out to standardize and clean up the internal and external 
> naming of the bookmarks API, and that should allow us to more cleanly make a 
> breaking change like this.

This is great to hear. Thank you!

Speaking of backwards compatibility, I'd again like to encourage Mercurial to adopt [Semantic Versioning](http://semver.org/):

> Given a version number MAJOR.MINOR.PATCH, increment the:
> 
>  1. MAJOR version when you make incompatible API changes,
>  2. MINOR version when you add functionality in a backwards-compatible manner, and
>  3. PATCH version when you make backwards-compatible bug fixes.

As someone who manages software upgrades, it is really nice to know, without reading release notes, how safe a new version of software is to upgrade by comparing the version I'm at with the version I want to upgrade to.