Last release v0.17.0 was proposed at the end of July. and the release day is 25 July, more detail refer v0.17.0 release schedule. It has been almost three months since July. According to our RFC-0067 about quarter-based releases, I hope to release v0.18.0 version at the end of Oct 2024. It's meaningful especially for AI infra companies which needs regularly merge with release version.In order to continue with our agreed release cycle as per discussion in RFC#67 , I'd like to propose a schedule for our next TVM release: v0.18.0.
This schedule is tentative and may change as we progress through the process. In case dates change, this thread will be kept updated.
The proposed schedule is:
[ ] 8 Oct. 2024 Following three actions should be continuous and coherent:
[ ] Make version modification twice as two commits: first to v0.18.0 on main branch; second to v0.19.dev0 on main branch in one PR, and merged without squash (required). Why do this first referring discuss on v0.14.0 release:
[ ] A branch v0.18.0 to be created from main on first commit:
[ ] A tag named v0.18.0.rc0 created on first commit:
[ ] A tag named v0.19.dev0 created on second commit:
[ ] 12 Oct. 2024 - Cherry-picking soft deadline
During this time any reasonable change can be merged, comment on this issue with the commit you would like added to the release branch
[ ] 16 Oct. 2024 - Cherry-picking hard deadline
During this time only critical changes will be merged, comment on this issue with the commit you would like added to the release branch as well as the reasoning for adding it
[ ] Create a new release tag v0.18.0 on last commit on release branch:
[ ] Change pre-release as latest release:
[ ] Upload the binaries to Apache mirrors:
[ ] 21 Oct. 2024 - Release date
[ ] 22 Oct. 2024 - Update the TVM Website
Call for release managers: In case you want to be involved in upcoming releases, please manifest your interest in this thread and we'll try to organise. 😆
This schedule is tentative and may change as we progress through the process. In case dates change, this thread will be kept updated.
The proposed schedule is:
v0.18.0on main branch; second tov0.19.dev0on main branch in one PR, and merged without squash (required). Why do this first referring discuss on v0.14.0 release:v0.18.0to be created frommainon first commit:v0.18.0.rc0created on first commit:v0.19.dev0created on second commit:v0.18.0.rc0and uploadingv0.18.0.rc0:v0.18.0on last commit on release branch:Call for release managers: In case you want to be involved in upcoming releases, please manifest your interest in this thread and we'll try to organise. 😆
See also:
cc @apache/tvm-committers @Hzfengsy @vinx13 @areusch @Mousius @tqchen @AndrewZhaoLuo @Johnson9009