- changed status to resolved
Incrementing a more significant version number part does not reset the lower parts
Issue #1
resolved
If your current version is 1.0.2, then performing an increment of the MINOR version number part should reset the PATCH number part back to zero.
For example, the current behaviour would be to change "1.0.2" to "1.1.2" with an increment of the MINOR version part, whereas the correct behaviour should be to change "1.0.2" to "1.1.0".
The same applies for increments to the MAJOR version number part which should reset both the MINOR and PATCH parts to zero.
Comments (1)
-
reporter - Log in to comment
Fixes
#1- As more significant parts of the version number are incremented, the lesser significant parts are reset to zero.→ <<cset 77ae1de1d571>>