[Release] v0.15.0 release schedule

[ysh329]

Last release v0.14.0 was proposed at the end of September and the release day is 23 Oct, more detail refer v0.14.0 release schedule. It has been almost three months since 1 Oct. According to our RFC-0067 about quarter-based releases, I hope to release v0.15.0 version at the end of January 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.15.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 Jan 2024 Following three actions should be continuous and coherent:
  • Make version modification twice as two commits: first to v0.15.0 on main branch; second to v0.16.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.15.0 and 0.16.0.dev on main branch #16326
  • A branch v0.15.0 to be created from main on first commit: https://github.com/apache/tvm/tree/v0.15.0
  • A tag named v0.15.0.rc0 created on first commit: https://github.com/apache/tvm/releases/tag/v0.15.0.rc0
  • A tag named v0.16.dev0 created on second commit: https://github.com/apache/tvm/releases/tag/v0.16.dev0
• 5 Jan 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
• 9 Jan 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
• 9 Jan 2024 - Draft release notes published: [Release] v0.15.0 Release Candidate Notes #16391
• 12 Jan 2024 - Prepare release candidate packaging v0.15.0.rc0 and uploading
  • Create tag v0.15.0.rc0: https://github.com/apache/tvm/releases/tag/v0.15.0.rc0
  • Github release page: https://github.com/apache/tvm/releases/tag/v0.15.0.rc0
  • Upload to Apache repo: https://dist.apache.org/repos/dist/dev/tvm/tvm-v0.15.0-rc0/
• 12 19 Jan 2024 - Release voting opens: [VOTE] Release Apache TVM v0.15.0.rc0 #16428
• 22 25 Jan 2024
  • Voting result: [RESULT][VOTE] Release Apache TVM v0.15.0 #16475
  • Create a new release tag v0.15.0 on last commit on release branch: https://github.com/apache/tvm/releases/tag/v0.15.0
  • Change pre-release as latest release: https://github.com/apache/tvm/releases/tag/v0.15.0
  • Upload the binaries to Apache mirrors:
• 22 25 Jan 2024 - Release date
• 22 25 Jan 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
• TVM release process docs.

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

[ysh329]

Hi all, make version modification twice as two commits in one PR merged (#16326). We need:

1. Create a branch named v0.15.0 from main on first commit(7445b87);
2. Create a tag named v0.15.0.rc0 on first commit(7445b87);
3. Create a tag named v0.16.dev0 created on second commit(e69363a).

I don't know how to push tags/branch created on my own repo to apache/tvm's? I didn't find about create branch by Web UI as below in apache/tvm:

[ysh329]

Hi all, make version modification twice as two commits in one PR merged (#16326). We need:

1. Create a branch named v0.15.0 from main on first commit(7445b87);
2. Create a tag named v0.15.0.rc0 on first commit(7445b87);
3. Create a tag named v0.16.dev0 created on second commit(e69363a).

I don't know how to push tags/branch created on my own repo to apache/tvm's? I didn't find about create branch by Web UI as below in apache/tvm:

Besides, I push tags and branch created by command line to my own repo. However, I don't know how to push to apache/tvm.

cc @Hzfengsy @vinx13 @tqchen

[vinx13]

@ysh329 a tag will be created automatically if you create a release on GitHub

[ysh329]

@ysh329 a tag will be created automatically if you create a release on GitHub

I found this Create a new release link in my own tvm repo:

but find nothing link about Create a new release below apache/tvm repo:

cc @Hzfengsy @vinx13

[vinx13]

@ysh329 you may need to setup your github account following https://cwiki.apache.org/confluence/display/OPENWHISK/Accessing+Apache+GitHub+as+a+Committer

[ysh329]

@ysh329 you may need to setup your github account following https://cwiki.apache.org/confluence/display/OPENWHISK/Accessing+Apache+GitHub+as+a+Committer

Oh, u r right.

[ysh329]

Hi all, may delay few days, may some issue when I register iCLA previous. I resend a register email. If anyone has cherry-pick PR, please notify in this thread.

[ysh329]

Hi all, make version modification twice as two commits in one PR merged (#16326). We need:

1. Create a branch named v0.15.0 from main on first commit(7445b87);
2. Create a tag named v0.15.0.rc0 on first commit(7445b87);
3. Create a tag named v0.16.dev0 created on second commit(e69363a).

Hi all, branch and tags created.

[ysh329]

Hi all, due to cherry-pick PR about release signing, I update the tag v0.15.0.rc0 to new commit: a340dbe.

[ysh329]

Hi all, vote starts (#16428). Everyone is welcomed to vote. Please vote by replying to this thread (#16428) explicitly. Vote will close Jan. 25th at 23:59M GMT.

[ysh329]

Hi all, github tag v0.15.0 created and release page updated. Please help update apache svn repo, because it need authority:

After the vote passes, to upload the binaries to Apache mirrors, you move the binaries from dev directory (this should be where they are voted) to release directory. This “moving” is the only way you can add stuff to the actual release directory. (Note: only PMC can move to release directory)
From doc about post the release: https://tvm.apache.org/docs/contribute/release_process.html?highlight=release#post-the-release

cc @Hzfengsy @junrushao @tqchen

I didn't find doc link from CI in last PR (#16424): https://ci.tlcpack.ai/blue/organizations/jenkins/tvm-arm/detail/PR-16424/1/pipeline, can u give me some prompt @vinx13