Add development versioning scheming #601
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
srittau
reviewed
May 21, 2025
Comment on lines
+28
to
+29
| After meaningful updates, but without concrete plans for a release, the version can pre increased once in [pyproject.toml](/pyproject.toml) file and appended with a `.dev` suffix, e.g. `4.0.1.dev`. | ||
| Further development versions adjust their suffix in following increasing way `.dev1`, `.dev2`, ... |
There was a problem hiding this comment.
I would suggest that we (and by that I mean our release manager, @JelleZijlstra), increase the version to .dev after each release, even without any updates in between. This makes is clear that the current version is not identical to the released PyPI package, and we don't forget to increment the version number after a "meaningful" update.
There was a problem hiding this comment.
Yeah, I wouldn't want to manually bump this version between releases. We can do some packaging magic to make the version show up as 4.5.6.dev+<commit hash> or something, I think that's what mypy does?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In relation to #528 I've written a proposal on how and vaguely when to add development versions.
I've oriented myself on the packaging versioning, and decided against the hyphen
-suffix for pre-releases.Further input and ideas are welcome.