mojombo/semver — Issue #9: Why is it so strict about resetting minor version to zero?
Author: vi
Created: 2012-01-04 10:08:58+00:00
State: open

... the minor version and patch version MUST be reset to zero.

What will break if the minor version is not reset to zero while incrementing the major version number? Not resetting it will allow to preserve more or less linear flow of versions on minor (but API breaking) change.

For example, in `1.5 -> 1.6 -> 1.7 -> 2.8 -> 2.9` we can talk about short "version 6" or "version 9" instead of saying the two numbers every time and psychologically rebasing the development to the beginning of major cycle ("2.0" it will seem like "completely new version with new API" rather than "next version + some API change").

May be better be `SHOULD be reset to zero` or `MUST be reset to zero or incremented by one`?