We plan to use SemVer style versions for tezos-ts but we will make the major version number track the version number of the supported economic protocol.
This would make our first version number v4.0.0 as it would support 004-Pt24m4xi
The next major version number (assuming Babylon is accepted) could be v5.0.0 which would correspond with 005-PsBABY5n
Outline;
Need for clear version numbers
Tension between SemVer and bumping major number even when API surface may not have big changes. (read, not SemVer but SemVer style).
alpha releases for new protos when proposal passes proposal phase
beta as soon as is responsible
final released prior to protocol transitioning to new protocol version.
All clients must be backward compatible with historic blocks all the way to genesis.
Support policy for versions will be current proto and proto+1.
Proto+1 releases should always be released a couple weeks prior to transition
jevonearth
commented
5 years ago
We plan to use SemVer style versions for
tezos-tsbut we will make the major version number track the version number of the supported economic protocol.This would make our first version number
v4.0.0as it would support004-Pt24m4xiThe next major version number (assuming Babylon is accepted) could bev5.0.0which would correspond with005-PsBABY5nOutline;