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 the release manager should be responsible for the release they published (and in the best case this would mean a release needs no patches and thus requires no extra work), but this could get passed off or reassigned as we move along based on who's available. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/67#issuecomment-1121422799 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/67/c1121422...@github.com>
