The https://github.com/CERTCC/SSVC/blob/main/docs/adr/0013-ssvc-project-versions.md captures current idea of how to do overall SSVC Project versioning uses CalVer. Currently PyPI version is not consistent as it requires server like tagging without the v in the beginning. So we have two versioning under a publish event.
I would like to make PyPi as well as the Publish versioning in our website https://certcc.githb.io/CERTCC/SSVC/ to be the same.
The semver versioning uses Major.Minor.Patch motif for versioning. We should just use YYYY.M.$patch for both PyPI and website version. If we do a new release and it is only a patch that has changed even though the month of release has changed, it will just look like a Minor update instead of just being a Patch. This is okay IMO.
The https://github.com/CERTCC/SSVC/blob/main/docs/adr/0013-ssvc-project-versions.md captures current idea of how to do overall SSVC Project versioning uses CalVer. Currently PyPI version is not consistent as it requires server like tagging without the
vin the beginning. So we have two versioning under a publish event.I would like to make PyPi as well as the Publish versioning in our website https://certcc.githb.io/CERTCC/SSVC/ to be the same.
The semver versioning uses Major.Minor.Patch motif for versioning. We should just use YYYY.M.$patch for both PyPI and website version. If we do a new release and it is only a patch that has changed even though the month of release has changed, it will just look like a Minor update instead of just being a Patch. This is okay IMO.