CODEWITHSUNDEEP
versioningsemantic-versioning
Goonyan Harir
Goonyan Harir

Reputation: 303

Versioning with SemVer

I need a bit of help/advice with versioning with SemVer.

I'm working on a client's website who has sent several related amends both large and small to his site in a word document (like they always do).

I have a branch based off my master branch for these new amends, and have created commits for each completed amend I have done so far.

The idea was that I would complete all of the amends and then release them in the next release (v2.0.0) because I think all of these changes are related and all of them combined are significant enough to warrant a bump in version number.

The issue I have is that the client wants a few of these amends to be made live immediately, before the release of 2.0.0, so what would the best way of handling this be - would I upload these few completed amends into the existing version and increment the minor number, or would I bump it up to 2.0.0 even though all of the amends aren't complete?

I am a bit of a noob when it comes to versioning, but am trying to learn as best I can by reading and trying to make sense of Semantic Versioning site.

Upvotes: 1

Views: 549

Answers (1)

Giordano
Giordano

Reputation: 311

You should always consider these two things:

  1. What the real changes are? If there are no visible changes, and/or if there are no major changes underneath, it may be better to avoid to increment the major version number.

  2. What the customer should perceive of your changes? Saying version 1.1 or version 2.0 may make some difference in how the changes are perceived.

So if the modifications are limited and/or there are no visible things that have changed, it may make sense to increment the minor only and then wait for all of them to be complete to bump it to 2.0.0.

Upvotes: 2

Related Questions