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.

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

Q: Why our releases jump from 0.1.4 to 0.1.15? #197

Closed
oesteban opened this issue May 20, 2024 · 5 comments
Closed

Q: Why our releases jump from 0.1.4 to 0.1.15? #197

oesteban opened this issue May 20, 2024 · 5 comments

Comments

@oesteban
Copy link
Member

With the latest release, we seem to have skipped a number of patch releases: https://pypi.org/project/eddymotion/#history

What was the rationale behind this? I don't think this is a big deal at this moment of the development of the package (other than renaming a milestone https://github.com/nipreps/eddymotion/milestone/4), but perhaps there was some blocker/problem that might have gone undetected.

cc/ @effigies @esavary

@effigies
Copy link
Member

I think it was probably a typo in the issue title:

@oesteban
Copy link
Member Author

Ha, you're right - that likely dragged the whole thing. Do we want to add some checks to the release pipeline and/or use setuptools_scm to suggest the new version name?

@effigies
Copy link
Member

The name is already being suggested:

hatch version
24.0.0.dev19

Do we have a release checklist? If so, I think updating that with clearer instructions would be sensible. If not, we could add one. PyBIDS has one we could start from: https://github.com/bids-standard/pybids/wiki/Release-Process

@effigies
Copy link
Member

I feel like writing checks will be a lot of work for very little gain.

@oesteban
Copy link
Member Author

Okay, nothing to do here. Let's just make sure we do not trust an issue title by me again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants