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.

@tqchen do you know any other alternative?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/15216#issuecomment-1623964859
You are receiving this because you are subscribed to this thread.

Message ID: <apache/tvm/pull/15216/c1623964...@github.com>

Reply via email to