Fix post-release development versioning #601
Merged
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.
docs/changelog.md
Summary of changes
For the post-release procedure / script, we append "dev0" so the version from git
master
is different than the released version.The way we currently do this (just append "dev0" onto last released version) is wrong, because in the PEP 440 scheme,
<version>.dev0
actually precedes<version>
.To fix this in the most expedient way, I changed the post-release script to append ".1.dev0" to the last release version instead of ".dev0". This ensures proper version ordering, at least with regard to the last released version.
Test plan
Tested by running