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.18.0 was proposed at the end of September. and the release day is 21 Oct., more detail refer v0.18.0 release schedule. It has been almost three months since September. According to our RFC-0067 about quarter-based releases, I hope to release v0.19.0 version at the end of Jan. 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.19.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 Jan. 2025 Following three actions should be continuous and coherent:
Make version modification twice as two commits: first to v0.19.0 on main branch; second to v0.20.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.19.0 to be created from main on first commit:
A tag named v0.19.0.rc0 created on first commit:
A tag named v0.20.dev0 created on second commit:
12 Jan. 2025 - 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 Jan. 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
Create a new release tag v0.19.0 on last commit on release branch:
Change pre-release as latest release:
Upload the binaries to Apache mirrors:
21 Jan. 2025 - Release date
22 Jan. 2025 - 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. 😆
The text was updated successfully, but these errors were encountered:
ysh329
added
type: bug
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
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
Dec 27, 2024
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.19.0
on main branch; second tov0.20.dev0
on main branch in one PR, and merged without squash (required). Why do this first referring discuss on v0.14.0 release:v0.19.0
to be created frommain
on first commit:v0.19.0.rc0
created on first commit:v0.20.dev0
created on second commit:v0.19.0.rc0
and uploadingv0.19.0.rc0
:v0.19.0
on 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
The text was updated successfully, but these errors were encountered: