Here, let me explan why do first version modification to v0.14.0 on main branch.
Considering downstream companies need regularly do code merge with release code, each time version modification is after cut branch. In other words, each version modification commit is not on git main tree (and after branch cut we do version modification on main, two branch divergence), which results in code conflict such as version number between codebase of downstream companies and latest upstream release. > In the previous practice, we didn't change tags into the release version on > the main branch. > > Pros: It will make the release branch a commit on the main branch, rather > than diverging from the commit line Cons: There might be commits after v0.14 > but before we change it to v0.15dev > > Happy to hear voices from the community Besides, for Pros point exists both in the previous and this proposed release process. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm/pull/15847#issuecomment-1752254682 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm/pull/15847/c1752254...@github.com>
