I see, I can see us doing that as well. We would need to have a clear fallback 
mechanism though for the generated files, as in cases when we want to build 
runtime only module and may not have a correct `setuptools_scm` dependency

Officially, we only release source code package on stable release. While 
provide convenient binary release tools so we can generate these release. I can 
see us still using the version.py to update the stable versions. Perhaps we 
could add another options to `version.py --scm-version` that directly queries, 
but not modify the files inplace. In that case it can be used to optionally 
gnerate artifacts.





---
[Visit 
Topic](https://discuss.tvm.ai/t/rfc-naming-scheme-for-tvm-versions-and-packages/6833/6)
 to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.ai/email/unsubscribe/1726dc238218b498c76f69cec8bb2d343d1eca334f74744209f58bec55b15e90).

Reply via email to