[Release] v0.24.0 release schedule

[ysh329]

Last release v0.23.0 was proposed at the end of Dec. and the release day is 8 Feb (little delayed). It has been almost three months since Jan. According to our RFC-0067 about quarter-based releases, I hope to release v0.24.0 version at the end of Apr. 2026. 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.24.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:

• 2 April. 2026 Following three actions should be continuous and coherent:
  • Make version modification twice as two commits: first to v0.24.0 on main branch; second to v0.25.dev0 on main branch in one PR, and merged without squash (required). Why do this first referring discuss on v0.14.0 release: [release][Dont Squash] Update version to 0.23.0 and 0.24.0.dev on main branch #18669
  • A branch v0.24.0 to be created from main on first commit: https://github.com/apache/tvm/tree/v0.24.0
  • A tag named v0.24.0.rc0 created on first commit: https://github.com/apache/tvm/releases/tag/v0.24.0.rc0
  • A tag named v0.25.dev0 created on second commit: https://github.com/apache/tvm/releases/tag/v0.25.dev0
• 7 April. 2026 - 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
• 12 April. 2026 - 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 Features Discussion before Next Release
• 12 April. 2026 - Draft release notes published: [Release] v0.23.0 Release Candidate Notes #18701
• 12 April. 2026 - Prepare release candidate packaging v0.24.0.rc0 and uploading
  • Create tag v0.24.0.rc0: https://github.com/apache/tvm/releases/tag/v0.24.0.rc0
  • Github release page from tag: https://github.com/apache/tvm/releases/tag/v0.24.0.rc0
  • Upload to Apache repo: https://dist.apache.org/repos/dist/dev/tvm/tvm-v0.24.0-rc0/
• 24 April. 2026 - Release voting opens: [VOTE] Release Apache TVM v0.23.0.rc0 #18702
• 28 April. 2026
  • Voting result: [RESULT][VOTE] Release Apache TVM v0.23.0 #18721
  • Create a new release tag v0.24.0 on last commit on release branch: https://github.com/apache/tvm/releases/tag/v0.24.0
  • Change pre-release as latest release: https://github.com/apache/tvm/releases/tag/v0.24.0
  • Move the binaries from candidate to release Apache mirrors: https://dist.apache.org/repos/dist/release/tvm/tvm-v0.24.0/
• 28 April. 2026 - Release date
• 28 April. 2026 - Update the TVM Website
  • Create a PR (ref: https://github.com/apache/tvm-site/pull/51/files) on main branch for tvm-site (from yourself owner repo): Add download links for version 0.23.0 tvm-site#55
  • Execute script on main branch for tvm-site (from apache owner repo): execute scripts/task_deploy_asf_site.sh auto-done by bot
  • Update doc with different version
  • https://dist.apache.org/repos/dist/release/tvm/tvm-v0.24.0/
  • https://www.apache.org/dyn/closer.lua/tvm/tvm-v0.24.0/

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
• TVM release process docs.

cc @apache/tvm-committers @Hzfengsy @vinx13 @areusch @Mousius @tqchen @AndrewZhaoLuo @Johnson9009 @yongwww

[LudovicoYIN]

hi, @ysh329. I’m interested in getting involved in the release process—are there specific tasks I can help with?

[ysh329]

hi, @ysh329. I’m interested in getting involved in the release process—are there specific tasks I can help with?

Hi YinHanke, absolutely no problem at all! If you’d like to get involved, you can just follow the timeline above to proceed. For example, you can submit a pull request for updating the version number, and so on. Just follow the timeline step by step.