@areusch helped me understand the contention here, there's a release process for managing things such as bugs, security vulnerabilities and other forms of fixes in a release cycle and accounting for all of those things in this roadmap is definitely out of scope :smile_cat:
My confusion was that "Security problems with TVM dependencies" and "Security vulnerabilities in the TVM code itself" can be monitored by automation, which is what I'm suggesting to include as part of this roadmap. The actual tactics of remediation for issues would be defined elsewhere, likely alongside release processes or as part of a another roadmap. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/54#issuecomment-1031909240 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/54/c1031909...@github.com>
