You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made the version string taken from the output of git describe --tags --long. It's OK if the tools were downloaded by doing git clone, but when the source was downloaded as a ZIP the version string becomes 0.0.0.
I think we need to add a GitHub hook to set the version string in setup.py for ZIP downloads, thought I know almost nothing about the hooks. (A negative/tempral solution would be to disable "Download ZIP")
The text was updated successfully, but these errors were encountered:
Why can't we just set up version manually? From my point of view, changing version is not something we do every day, therefore I think it's OK to do it manually when we decide to do it.
As far as I know, even in such a large project like Plone they recommend to do it manually, llike, for instance, in this setup.py.
I think it's OK to manually set the version number if you release only some selected/tagged commits as tarballs/zips. But cloned source files from an open repository differ for every commit, and therefore I think it's better to assign every commit a version tag for identification. I also tend to forget rewriting the version number for some files... ;-<
I made the version string taken from the output of
git describe --tags --long
. It's OK if the tools were downloaded by doinggit clone
, but when the source was downloaded as a ZIP the version string becomes0.0.0
.I think we need to add a GitHub hook to set the version string in
setup.py
for ZIP downloads, thought I know almost nothing about the hooks. (A negative/tempral solution would be to disable "Download ZIP")The text was updated successfully, but these errors were encountered: