A
A
Andrey Kolechko2019-05-29 18:44:19
git
Andrey Kolechko, 2019-05-29 18:44:19

What version to specify when updating a project?

For example, I am running a project. Let the initial version be v1.0.0. Added a commit, and the project has changed, you need to give a new version. By what criteria is this done? Obviously, let's say that if the project has changed dramatically, then version v2.0.0 is given, but what if not much? When should you install, say, v1.3.0, v1.0.9? Are there clear rules on how a new version is assigned? Or is everything done by eye? After all, there are also versions larger than three-digit ones.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
K
kova1ev, 2019-05-29
@AnkoII

backward compatibility between versions is lost - change the first digit
new functionality is added - change the second digit
bugs are fixed - change the third digit

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question