Answer the question
In order to leave comments, you need to log in
How to create a product version?
What are the criteria for assigning a version to a product? I saw versions like v1.15.92.3.1 from other developers, but for most they contain no more than 3 digits like v1.4.5.
Perhaps someone has a ready-made system where you can read about it?
Answer the question
In order to leave comments, you need to log in
npm
has the following convention:
1.0.0 - initial stable version
1.0.1 - patch release, small fixes, functionality does not change
1.1.0 - minor release, adding new functionality, old functionality is supported
2.0.0 - major release, new functionality, not saved support for previous versions
[link]
We open the browser.
We open the search engine.
We enter "versioning".
We press search.
Just in case, as an example, here is one of the search results.
some assign a version in the form of a year, month and day, and at the end a unique number - if more than one patch was released per day.
It all depends on your inner world. Race browsers once scored on the principles of versioning - like "more is better". And even fixed releases began to be marked by increasing the first digit. Chrome started to do this - well, then all browsers joined this race. After all, chrome v67 is better than firefox 60? It's the fucking marketers who made versioning hell.
So it's up to you to choose - whether you will have your product v0.01 at the first release or immediately v1.0 and the second release immediately v3.0 - for example, php was engaged in such jumps - skipping v6.0 and immediately releasing 7.0. True, they say that there were other reasons for that ....
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question