Version archives for release #1148
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.
This adds a VERSION file in the root containing a template that is filled out with the current version by git when a tarball is created using
git archive. It also extends the Python package builds to use that version if we're not building from a git repository.Note that git looks only for full git tags, not lightweight ones as we've been using so far. So this will require using
git tag -a vxxxx.y.zto tag releases from now on. There's an option to also take lightweight tags into account, but it seems to be broken. Anyway, for tagging releases full tags are the standard, so we might as well do that.With this merged and releases tagged appropriately, users will be able to install from a tarball, which saves download time and bandwidth and can be done with curl, which is available by default on macOS and most Linux installations and so saves an additional git installation step.