Sure! Modifiers are a pretty common practice in versioning. A practical example:
All my versions of boltons are CalVer with no modifier. However, the GitHub version's setup.py should always have a dev modifier. This way when someone reports a bug and their version has dev in it, I can tell they weren't using a release version, and I can respond accordingly (e.g., tell them to use a release version).
It's not at all specific to CalVer, but it's a very pragmatic pattern, and I encourage it :) Does that help?
Sure! Modifiers are a pretty common practice in versioning. A practical example:
All my versions of boltons are CalVer with no modifier. However, the GitHub version's setup.py should always have a
devmodifier. This way when someone reports a bug and their version hasdevin it, I can tell they weren't using a release version, and I can respond accordingly (e.g., tell them to use a release version).It's not at all specific to CalVer, but it's a very pragmatic pattern, and I encourage it :) Does that help?