+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/68#issuecomment-1121769448
You are receiving this because you are subscribed to this thread.
Message ID:
Thanks @Mousius for the great and insightful feedback.
Let's split your feedback into two concerns which we can address separately:
* **C1: Using TVM roadmaps to track work outside of TVM mainline**
The
[guidelines](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0050-roadmaps.md)
for Roadm
I agree with @areusch that a lot changes pre and post 1.0. This RFC's main
focus is getting code out the door often, so with that I think it makes the
most sense to only support the current version and only publish a new release
mid-cycle for critical bug fixes and security issues.
Ostensibly t
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/68#issuecomment-1121104485
You are receiving this because you are subscribed to this thread.
Message ID:
I think this is great. Let's leave the RFC open for a couple days more, in case
anyone has anything to add, and then merge it.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/68#issuecomment-1121054917
You are receiving this because you are subscribe
