Release tagging

[ARR4N]

Axioms

Release tags should:

1. Capture the geth version (for humans);
2. Capture the libevm version (for humans);
3. Conform to semver (for Go tooling)

Recommendation

I suggest that we inherit the geth major.minor.patch and extend it with a libevm triplet as a prerelease. Examples:

• Start: 1.13.14-0.1.0
• Add feature: 1.13.14-0.2.0
• Bump geth: 1.14.9-0.2.0 or 1.14.9-0.3.0 etc as appropriate (TBC)

Rationale

1. This maintains a lexical ordering that is in keeping with the flow of development over time.
   a. Inverting geth-libevm as libevm-geth would still be monotonic, but doesn't feel natural as geth changes are more substantial.
2. As a prerelease, we make no guarantees of stability.

Open questions

1. Are there other requirements?
2. Are there better tagging patterns? What is better about them?