OpenSource library-versioning

Part 1

Implement Open-source library guidance

Part 2

OpenSource library – Cross-platform targeting

Part 3

OpenSource library-Dependencies

Part 4

OpenSource library- Source Link

Part 5

OpenSource library-versioning

Part 6

OpenSource library- Breaking changes

Part 7

OpenSource library- conclusion

Following recommendations from https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/versioning

Nr

Recomandation

AOP Roslyn

1

CONSIDER using SemVer 2.0.0 to version your NuGet package.

 NO

2

DO use the NuGet package version in public documentation as it’s the version number that users will commonly see.

 Yes

3

DO include a pre-release suffix when releasing a non-stable package.

 No

4

CONSIDER only including a major version in the AssemblyVersion

 Yes

5

CONSIDER keeping the major version number of the AssemblyVersion and the NuGet package version in sync.

 Yes

6

DO NOT have a fixed AssemblyVersion

 Yes

7

CONSIDER including a continuous integration build number as the AssemblyFileVersion revision

 Not needed

8

AVOID setting the assembly informational version yourself.

 Yes

For 1: I do not like SemVer. It is putting some pressure on the developer of the OpenSource. So I decide to follow Calendar versioning https://calver.org/ 

For 2: Yes, it is normal.

For 3: No, I do not like pore-release.

For 4: Yes – the year is major

For 5: Yes, done by CI process

For 6: Yes, done by CI in Calendar Versioning

For 7: NO. And , because of Calendar versioning, it is already done, if I do not publish 2 versions in the same day

For 8: Do nothing – and it is done.