Open oesteban opened 1 year ago
I think we have 3 version schemes in use:
1) Calver (YY.MINOR.PATCH) 2) Semver (MAJOR.MINOR.PATCH) 3) Pre-1 semver (0.MINOR.PATCH)
We should select/create setuptools_scm version schemes for each case and make clear how to use it. I would suggest that production-ready apps use calver, libraries use semver, and anything that's not production ready use pre-1 semver.
What would you like to see added in this software?
Should this template be added nipreps/version-schemes?
cc/ @effigies @mgxd
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response