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.16.0.
I suggest we keep the discussion in the GitHub issue I opened for this topic.
opened 07:00AM - 09 Apr 24 UTC
> [Last release v0.15.0](https://github.com/apache/tvm/issues/16277) was propose… d at the end of Jan. and the release day is 25 Jan, more detail refer [v0.15.0 release schedule](https://github.com/apache/tvm/issues/16277). It has been almost **three months** since Jan. According to our [RFC-0067 about quarter-based releases](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md), I **hope to release v0.16.0 version at the end of April 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](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md) , I'd like to propose a schedule for our next TVM release: `v0.16.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:
- [ ] **12 Apr. 2024** Following three actions should be continuous and coherent:
- [ ] Make version modification twice as two commits: first to `v0.16.0` on main branch; second to `v0.17.dev0` on main branch in one PR, and **merged without squash (required)**. Why do this first [referring discuss on v0.14.0 release](https://github.com/apache/tvm/issues/15134#issuecomment-1607649151):
- [ ] A branch `v0.16.0` to be created from `main` on first commit:
- [ ] A tag named `v0.16.0.rc0` created on first commit:
- [ ] A tag named `v0.17.dev0` created on second commit:
- [ ] **15 Apr. 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
- [ ] **20 Apr. 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
- Consider https://github.com/apache/tvm/issues/16719
- [ ] **20 Apr. 2024** - Draft release notes published:
- [ ] **20 Apr. 2024** - [Prepare release candidate packaging `v0.16.0.rc0` and uploading](https://tvm.apache.org/docs/contribute/release_process.html#upload-the-release-candidate)
- Create tag `v0.16.0.rc0`:
- Github release page from tag:
- Upload to Apache repo:
- [ ] **20 Apr. 2024** - Release voting opens:
- [ ] **25 Apr. 2024**
- [ ] Voting result:
- [ ] Create a new release tag `v0.16.0` on last commit on release branch:
- [ ] Change pre-release as latest release:
- [ ] Upload the binaries to Apache mirrors: <link>
- [ ] **26 Apr. 2024** - Release date
- [ ] **26 Apr. 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. 😆
See also:
- [Release steps](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md#reference-level-explanation)
- [TVM release process docs](https://tvm.apache.org/docs/contribute/release_process.html).
cc @apache/tvm-committers [@Hzfengsy](https://github.com/Hzfengsy) [@vinx13](https://github.com/vinx13) [@areusch](https://github.com/areusch) [@Mousius](https://github.com/Mousius) [@tqchen](https://github.com/tqchen) [@AndrewZhaoLuo](https://github.com/AndrewZhaoLuo) [@Johnson9009](https://github.com/Johnson9009)
