![]() Local version, it means how many local changes, not pushed commits for instance, were made.īack to the initial problem, from its many solutions, I found best to input git info into the dll version, and make it automatic, then there is no chance to forget doing it.I find those three numbers enough, along with the trick I’ll show you next, but a fourth number at right might be useful: Increase revision version after minor changes, like bug fixes, organization commits etc.Increase minor version whenever you add a new feature which is backwards compatible.Usually those are great changes and this number shouldn’t be increased often. Increase major version whenever the changes aren’t backwards compatible. ![]() I like to use three numbers,, starting at 1.0.0 it progresses like that: There are some guidelines, and a lot of discussion out there, but in the end, the team should choose what works best for them. Versioning is a common problem in software development, however, there isn’t a consensus about how to properly version a project. Version numbers alone didn’t solve it, but let’s talk about them first. The project had many independent contributors, and was deployed to a few different environments, what triggered a few versions from local branches. Hello again! Recently I faced the problem that I needed to recover the code, which generated a dll, only by looking at the dll itself.
0 Comments
Leave a Reply. |