My current situation: I would like to apply this to a solution containing multiple projects (one executable and different libraries) in C#. Additionally, I have a project that packs the executable, libraries and the .NET (currently v6.0) framework into an MSI installation package, which name should contain the product version. Other experiences: I have different…
How do I properly apply semantic versioning if I have more than three components in my version?
I am preparing a software package for internal consumption in my organization. It will be published on our internal non-public npm feed.
How to differentiate versioning between changes on version 1.0 and adding new features towards 2.0?
If I met all requirements on version 1.0 and go on working towards version 2.0, new features would be 1.1, 1.2, 1.3, and so on. What do I version the commits that represent an important fix or a forgotten feature which is required in version 1.0? Even if I didn’t version fixes on version 1.0, there would still be two version 1.0.1s until the develop branch merges into the master branch.
Semantic Versioning – going from one major version to another?
How should versions be bumped during development between two major versions?
For example let say I have version 1.5.0
and my target is to release new major version that will be incompatible with major version 1.