I'd change the patch version if it turns out that the tests weren't that thorough after all and there's e.g. a version upgrade of a dependency that's proven downwards-compatible. if it's not clear whether an upgraded dependency version is downwards-compatible) or even definitely (replacing JUnit4 with JUnit5, for instance). As a first approach I'd change the major version for changes that cause builds to fail potentially (e.g. It's entirely up to you which change increases the major, minor or patch version number. x.y.z release version if every work is finished, tested thoroughly and hence ready to be released into the wild. ![]()
0 Comments
Leave a Reply. |