Semantic Versioning for sop
This initial series is just the start of semantic versioning for sop itself, inspired by what we've learned from sopv.
Most crucially (from the diff):
sopversioning aims for each subsequent version of the specification to provide two things:
- a reasonable collection of functionality for some consumers of the
sopinterface, and- a reasonable next step for a piecemeal implementation of the entire
sopinterface
This series starts with a simple series, where each level adds the following feature bundles on top of the previous one:
- 1.0:
sopv1.0 + keygen + signing - 1.1:
sopv1.1 - 1.2: data handling (
armor/dearmor/inline-detach) - 1.3: secret key locking/unlocking
Future feature bundles that don't introduce a semver incompatibility will probably be:
- encryption + decryption
-
sopv1.2 + certification
(though i haven't decided what order to put those in)
Note that this series also deprecates/removes the apparently unusable sop version --sop-spec option.
Feedback welcome!
Edited by Daniel Kahn Gillmor