Vulkan ErupteD breaking changes and transition strategy

[Seb]

On Monday, 26 March 2018 at 07:04:00 UTC, Anton Fediushin wrote:
> This is a *bad* idea and you shouldn't do that.
>
> Just increase MAJOR version and start from there:
>
> 2.0.0 - Changing how binding works, Vulkan v1.0.69
> 2.1.0 - Vulkan 1.0.70
>
> ...And so on. This way semver is followed and you don't have to 
> mess with erupted-v1 and erupted-v2 repos.

Also note that SemVer allows to attach meta data:

2.0.0+1.0.69

> Build metadata MAY be denoted by appending a plus sign and a 
> series of dot separated identifiers immediately following the 
> patch or pre-release version. Identifiers MUST comprise only 
> ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST 
> NOT be empty. Build metadata SHOULD be ignored when determining 
> version precedence. Thus two versions that differ only in the 
> build metadata, have the same precedence.

https://semver.org/#spec-item-10