NuGet version is gone, and there will be changes...

[GeertvanHorrik]

So GitVersion_NuGetVersion is gone but can be used by "LegacySemVerPadded". Apparently it will be changed for v3, so the idea is to introduce 2 new variables:

GitVersion_NuGetVersionV2 => synonym for LegacySemVerPadded
GitVersion_NuGetVersionV3 => synonym for ???

[JakeGinnivan]

Or we can just bring back NuGetVersion then when v3 drops we release v2 of GitVersion which switches NuGet from LegacySemVerPadded to SemVer?

[GeertvanHorrik]

To make it backwards compatible for me I added this code to the VariableProvider class:

            {"NuGetVersion", semanticVersion.ToString("lp", formatter)}, // synonym for LegacySemVerPadded
            {"Version", semanticVersion.ToString("l", formatter)}, // synonym for LegacySemVer

[JakeGinnivan]

Not sure bringing back Version is a good idea, it is too vague?

The other thing is should we pad the NuGet version by default, or should we have a NuGetPadded

[JakeGinnivan]

The padded is only needed if you have tags greater than 10. i.e

-beta11

[SimonCropp]

unfortunately we cannot determine when padding will be needed. so we always add it

[GeertvanHorrik]

It's just so I can go on vacation in 2 hours and I don't have to change a zillion of builds. I am not saying Version should go back in the official version, I have just built my own version for the sake of backwards compatibility.

I prefer padding all the time instead of switching when the moon and sun are on the same level but only in August.

[GeertvanHorrik]

And what does "0.2.0-unstable.10+10" mean? I can understand the 10 (that is the no of commits), but +10?

[SimonCropp]

given nugets history of dodgy versioning i suspect there will be more dodgy work arounds that will need to be applied to future nuget implementations of semver. so i am leaning towards naming them explicitly like @GeertvanHorrik NuGetVersionV2 and perhaps have a NuGetVersionLatest (or something similar) that targets the current release version of nuget

any drawbacks people can see? thoughts?

[JakeGinnivan]

@GeertvanHorrik how did you get that version number? For develop you should get 0.2.0.10-unstable

Lets take a beta. 0.2.0-beta.1+10 means the first beta (i.e no tags on the release branch) and 10 commits since the branch was taken. When you tag 0.2.0-beta.1 then the version will become 0.2.0-beta.2+11

[JakeGinnivan]

@SimonCropp I am happy with adding NuGetVersionV2 for now, then when v3 drops we figure it out then.

OR we just add NuGetVersion back now, and it is for the latest version of NuGet. So when NuGet v3 drops we go to v2 and have a breaking change

[JakeGinnivan]

@GeertvanHorrik basically the +metadata is a way to include additional metadata which doesn't change the semantic version. so 0.2.0-beta.1+10 == 0.2.0-beta.1+20 from a SemVer point of view

[GeertvanHorrik]

It's the result of SetBuildVersion call. When I debug with this url:

/url https://github.com/Orcomp/C5Intervals /b develop /output buildserver

Caused by a call to semanticVersion.ToString("f")

[JakeGinnivan]

Interesting, I think that is a bug possibly. But that is a separate discussion

[GeertvanHorrik]

@JakeGinnivan Created new issue for the possible bug: #202