> created https://github.com/apache/tvm/tree/rc-v0.13.0, and confirmed that it
> do not have protection. as long as v0.13.0 prefix exists the branch is still
> protected.
>
> Let us send the PR there and do the release, then we can create a branch
> later, likely need to do so with manual push.
Yes, checkout https://github.com/mlc-ai/mlc-llm which uses relax and relies on
dynamic shape for LLMs
---
[Visit
Topic](https://discuss.tvm.apache.org/t/does-relax-support-dynamic-graph-inferring-on-gpu-now/15252/2)
to respond.
You are receiving this because you enabled mailing list mode
created https://github.com/apache/tvm/tree/rc-v0.13.0, and confirmed that it do
not have protection. as long as v0.13.0 prefix exists the branch is still
protected. Let us send the PR there and do the release, then we can create a
branch later
--
Reply to this email directly or view it on GitH
I think for next releases we should create a branch which doesn't conform the
with pattern that gets automatically protected, and instead, create something
like `v0.15.0-rc0`. Once everything is settled, then we just mark that as the
official branch, otherwise, we'll always face this issue.
@tq
cc @tqchen
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/15216#issuecomment-1623196204
You are receiving this because you are subscribed to this thread.
Message ID:
> Hi all, this PR #15216 `about modifying the version recorded to v0.13.0 on
> v0.13.0 branch` **is blocked by CI**, but this won't block our
> `cherry-picking soft deadline` and `cherry-picking hard deadline`.
>
> cc @driazati
Can anybody help to see the CI issue? It seems these thing block th
