Vulkan ErupteD breaking changes and transition strategy

[Seb]

On Monday, 26 March 2018 at 09:04:20 UTC, Anton Fediushin wrote:
> On Monday, 26 March 2018 at 07:51:31 UTC, Seb wrote:
>> 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
>
> That'll work too, but I'm not sure how dub handles it. Anyway, 
> even a little note in release description "Vulkan API vX.X.X" 
> should be enough.

It will work fine with dub (it just ignores the meta data).
For example, if you do a `dub add-local`, your package version is 
"+ annotated" with the git commit sha.