You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last release v0.19.0 was proposed at the end of January. and the release day is 27 Jan., more detail refer v0.19.0 release schedule. It has been almost three months since January. According to our RFC-0067 about quarter-based releases, I hope to release v0.20.0 version at the end of April. 2025. 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.20.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 April. 2025 Following three actions should be continuous and coherent:
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 18 April. 2025 - 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
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. 😆
The text was updated successfully, but these errors were encountered:
ysh329
added
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
type: bug
and removed
type: bug
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
labels
Mar 24, 2025
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.20.0
on main branch; second tov0.21.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.20.0 and 0.21.0.dev on main branch #17825v0.20.0
to be created frommain
on first commit: 1c60502, https://github.com/apache/tvm/tree/v0.20.0v0.20.0.rc0
created on first commit: https://github.com/apache/tvm/releases/tag/v0.20.0.rc0v0.21.dev0
created on second commit: https://github.com/apache/tvm/releases/tag/v0.21.dev01618 April. 2025 - Cherry-picking hard deadlineConsider Features Discussion before Next Release1618 April. 2025 - Draft release notes published: [Release] v0.20.0 Release Candidate Notes #178601618 April. 2025 - Prepare release candidate packagingv0.20.0.rc0
and uploadingv0.20.0.rc0
: https://github.com/apache/tvm/releases/tag/v0.20.0.rc01618 April. 2025 - Release voting opens: [VOTE] Release Apache TVM v0.20.0.rc0 #178612224 April. 2025v0.20.0
on last commit on release branch:2224 April. 2025 - Release date2224 April. 2025 - Update the TVM Websitescripts/task_deploy_asf_site.sh
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 @yongwww
The text was updated successfully, but these errors were encountered: