S
S
solascriptura2017-04-30 19:20:16
PHP
solascriptura, 2017-04-30 19:20:16

What is the best way to number releases?

Where can I read, or tell me from your experience, what is the best way to name the program version numbering?
For example, there are several services in production, but work is being done on them regularly, so far the thoughts on numbering are as follows:
The version number is 4 numbers separated by dots, (for example: 1.2.3.4), where increasing the number means:
1. (example: 2.0 ) Global release: when the entire service is rewritten from scratch. With design changes, APIs, etc.
2. (example: 1.2) Another release of version 1, in which a lot has changed, the interface could change. The API, when changed, could lose some of the backward compatibility, etc.
3. (example: 1.2.1) Sub-release 1.2. Minor changes, mostly bug fixes plus some new features. Full API backwards compatibility.
4. (Example: 1.2.1.38) Internal sub-release (I don't know if the term release is applicable in this case), the next step towards the release of version 1.2.2. In the sale, the numbers after the third link do not appear anywhere.
This is what I came up with at the moment, but maybe there are some standards for how it should actually be? Please correct my scheme, especially if there are serious miscalculations in it.
Thanks in advance )

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
solascriptura, 2017-04-30
@solascriptura

semver.org/lang/ru
It turns out there is a Russian version of the official site))))

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question