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

MAINT: update release protocol --> versioning scheme #1197

Closed
sappelhoff opened this issue Nov 20, 2023 · 4 comments · Fixed by #1259
Closed

MAINT: update release protocol --> versioning scheme #1197

sappelhoff opened this issue Nov 20, 2023 · 4 comments · Fixed by #1259
Assignees
Labels
Milestone

Comments

@sappelhoff
Copy link
Member

For future releases, we should follow https://semver.org/ more closely and always add the patch version as well. That is, 0.14 would be 0.14.0.

See discussion here:

@hoechenberger
Copy link
Member

With #1204, we'll only need to tag the version in the VCS for a release. Just saying that this needs to be reflected in the release protocol as well – no more manual version bumping

@sappelhoff
Copy link
Member Author

We should also add an "automated workflow to publish to pypi" upon making a GH release based on a tag.

@hoechenberger
Copy link
Member

We should also add an "automated workflow to publish to pypi" upon making a GH release based on a tag.

Maybe it's a good time to tackle this now as we'll need to release 0.15 sometime soon anyway

@hoechenberger hoechenberger added this to the 0.15 milestone Mar 26, 2024
@sappelhoff sappelhoff self-assigned this Jun 3, 2024
@sappelhoff
Copy link
Member Author

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

Successfully merging a pull request may close this issue.

2 participants