Is your feature request related to a problem? Please describe.
Since the version on the develop branch is the latest released version, it is difficult to verify what version am i using when I install from the develop branch that already contains new commits. Plus, pip doesn't overwrite the installed package if the existing the new version numbers are the same.
Describe the solution you'd like
After a version is released and the tag is merged back to develop, update the version number in the relevant files on the develop branch by appending a build number. Eg the released version is 0.8.0 and when merged back to develop it becomes 0.8.1-0001 or sth. No need to create a git tag. Increment the build number when commiting onto develop.
Remove the build number from the version on release so it becomes 0.8.1.
Describe alternatives you've considered
Stay business as usual.
Is your feature request related to a problem? Please describe. Since the version on the develop branch is the latest released version, it is difficult to verify what version am i using when I install from the develop branch that already contains new commits. Plus, pip doesn't overwrite the installed package if the existing the new version numbers are the same.
Describe the solution you'd like After a version is released and the tag is merged back to develop, update the version number in the relevant files on the develop branch by appending a build number. Eg the released version is
0.8.0and when merged back to develop it becomes0.8.1-0001or sth. No need to create a git tag. Increment the build number when commiting onto develop.Remove the build number from the version on release so it becomes
0.8.1.Describe alternatives you've considered Stay business as usual.