Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Versioning support #1

Open
oesteban opened this issue Feb 27, 2023 · 1 comment
Open

Versioning support #1

oesteban opened this issue Feb 27, 2023 · 1 comment
Assignees
@esavary
Labels
enhancement New feature or request

Comments

@oesteban
Copy link
Member

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
@oesteban oesteban added the enhancement New feature or request label Feb 27, 2023
@effigies
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@esavary esavary

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@effigies @oesteban @esavary