Answer the question
In order to leave comments, you need to log in
How to change the version correctly?
Moderators, correct me please!
Hello! Please tell me how to update the version correctly? Let's say the first version is 0.1 for me, if I release the second version, what should be the version? If let's say I have the first version like this 1.0.0, how can I write it correctly when there will be a second version, right? 1.1.0
Answer the question
In order to leave comments, you need to log in
Briefly (1.2.3):
1. Major version - contains irreversible consequences. It's like the difference between 2 and 3 Sonya.
2. Minor - major changes that complement, rather than cross out all the work in the major. It's like releasing a custom gamepad for Sonya.
3. Patch - contains mostly hotfixes.
Further on with examples:
1. Version 0.1.0 - says that you don't know what the fuck you are doing, but this is something that can be useful. As soon as it stabilizes, it rolls over to version 1.0.0. Before that, you introduce features → increase the minor, fix bugs - increase the patch. In principle, everything is the same as in other majors.
But in fact, everyone does what they want, because in essence semantic versioning is applicable to public APIs, which allows you to accurately track when your code built on this apa broke. I mean, there are also letter designations, it’s fun there and far from necessary everywhere.
Well, something didn't come out very briefly, but it should be more accessible than in the documentation and on Wikipedia.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question