Merge #53: Add docs about implied pre-release

c3bd3c2 Add docs about implied pre-release (Tobin C. Harding)

Pull request description:

  On `crates.io` our releases show up in yellow, implying they are
  pre-release versions. This is because of the `-` in our version number.

  Add docs explaining the version numbering to make explicit that the recent
  releases are not pre-releases.

ACKs for top commit:
  apoelstra:
    ACK c3bd3c2

Tree-SHA512: 0b7c609b1fd12c9c3325dc8fe84d924ee158e5330268b1e1aa0132564570ac35c4b43dd3348b1ffc4576e21d0b49fcac3db0f43b2ca482bb383006604e300cd9

Author: apoelstra

README.md

@@ -18,6 +18,14 @@ The project [rust-secp256k1](https://github.com/rust-bitcoin/rust-secp256k1) off
 This introduces a risk, since a difference between the two secp256k1 sources could break consensus with Bitcoin.
 
 
+## Version numbers
+
+We use [slightly abuse] semantic versioning. The first `Major.Minor.Patch` number tracks the vendored Bitcoin Core code (see below), the second `Major.Minor.Patch` tracks this crate. 
+For example, if we upgrade the Bitcoin Core code by a `Patch` version we also bump our `Patch` version.
+
+One side effect of this is that `crates.io` shows our release versions in yellow as if they were pre-release versions, this is due to us using a `-` which, in semantic versioning, implies a pre-release version.
+
+
 ## Bitcoin Core subtree
 
 We use a git subtree to vendor the Bitcoin Core code. This can be seen from the following commits that were created using `git subtree add --prefix='depend/bitcoin' git@github.com:bitcoin/bitcoin.git v0.19.2 --squash`.