leandron opened a new pull request #9472: URL: https://github.com/apache/tvm/pull/9472
Make `version.py` to rely on repository metadata to generate version string: * This change removes the need for a hardcoded version string (in `version.py`) when generating a TVM release from a `git` repository. The long term goal here is to be able to have reproducible release versions without manual intervention on files such as `version.py`. * It also removes assumptions of what the last valid tag should be, in order for the version string to be generated. This information should be encoded in the repository, as we are already using git tags to retrieve that information. **Important**: before merging this change we need to tag the beginning of `0.8` development cycle with the appropriate tag, so that the metadata is encoded in the repository. Here is the revision we need to tag: ``` git tag v0.8.dev0 a644e29735c043d6c8614d2d7fbe1eac7307d08e ``` Also, when `0.9` starts (or something else _e.g._ `1.0`), we need to tag it, so development versions are correctly generated. cc @mshawcroft @tqchen @areusch @Mousius @mbaret @gromero for reviews -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
