Just to clarify what is missing: is it updating (e.g. via `version.py`) the
version numbers in the source package so that it reflects the right version
when built?
@driazati I'm asking because this seems like a reasonable step, but it is not
what is instructed at
https://tvm.apache.org/docs/co
### Issue
Currently, StructInfo can use a local variable to express shape information.
However, this causes a visibility problem when we output with such StructInfo
to the outer scope of the current block.
### Reproducible Example
`Reshape` is the representative example.
```
# from tvm.scrip
The version numbers should reflect the current version (and it's in more places
than `version.py`). There should be a PR against the v0.11.0 branch like #12190
that updates the version numbers from `v0.11.0` to `v0.11.1`, then we tag that
commit once it's merged as the new v0.11.1
--
Reply to
okay i took a look here and i think something is messy with our process. here
is the process now:
1. cut a release branch, then update the checked-in version strings by running
`python3 version.py`, then creating a PR out of the diff. that typically should
look like https://github.com/apache/tvm
