+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/16368#issuecomment-1882129388
You are receiving this because you are subscribed to this thread.
Message ID:
+1 looking forward it can be landed as soon as possible.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/15521#issuecomment-1673451163
You are receiving this because you are subscribed to this thread.
Message ID:
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/102#issuecomment-1664847392
You are receiving this because you are subscribed to this thread.
Message ID:
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/15313#issuecomment-1635706867
You are receiving this because you are subscribed to this thread.
Message ID:
Can anybody help to see the CI issue? It seems these thing block the process of
release schedule several times.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/15216#issuecomment-1622912821
You are receiving this because you are subscribed to this thread.
Can below two steps be merged into one? Because these steps have some
relationship, i.e., the commit of "v0.14.dev0" must be the next commit of
branch v0.13.0, in addition these two steps can be done quickly as long as the
contributor has enough permission.
> 1 July 2023 - a branch v0.13.0 to b
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14710#issuecomment-1539311569
You are receiving this because you are subscribed to this thread.
Message ID:
@ysh329 After cherry-picked PRs, the version of TVM need to be updated to
"v0.12.0", like what we discussed at
https://github.com/apache/tvm/issues/14260, thanks.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14505#issuecomment-1519341462
You are rec
@ysh329 Can we align capital and small letter with [TVM v0.11.0 Release
Candidate Notes](https://github.com/apache/tvm/issues/13899) ? Like changing
"tvmscript" as "TVMScript", "microtvm" as "microTVM".
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/1
@ysh329 Thanks for bring this up, upgrade with official timely is good for the
downstream companies, especially for companies like ARM China whose customers
want to use the newest release version timely.
Thanks for excellent work of TVM community, ARM China built our heterogeneous
execution pro
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14260#issuecomment-1473064922
You are receiving this because you are subscribed to this thread.
Message ID:
+1, by the way the version is still 0.11.0dev, this should be changed to 0.11.1
too.
Actually, I want 0.12.0 more, because the 0.11 branch is behind too much than
main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/14260#issuecomment-1463999760
You a
Can we ensure a date that this release will be completed? So the downstream
organization can decide whether sync this release to our internal or not,
thanks.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/13586#issuecomment-1410128113
You are receivin
@driazati Understand, thanks.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12832#issuecomment-1275540306
You are receiving this because you are subscribed to this thread.
Message ID:
Does the release do more extra testing than the branch main?
In general, the release process contains two kinds of works, the first one is
arrangement, like we have done here, e.g, release note, license confirmation,
..., the other one is testing, some company or organization may use the work
"s
+1
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/8928#issuecomment-914032938
16 matches
Mail list logo
