[release] v0.10.0 Release Schedule

[AndrewZhaoLuo]

As discussed in https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md, releases will happen roughly every three months. I have been put in charge for this one. This thread is meant to discuss the release schedule.

We will do a branch cut soon but accept cherry-picked changes for a couple weeks.

See the release steps for details as well as the TVM release process docs.

The current schedule is:

• September 20 - branch cut
  • we will create a v0.10.0 branch from main on this day
  • Done: https://github.com/apache/tvm/tree/v0.10.0
  • Last commit: b051cad
• September 27 - 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
• September 30 - 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
• October 4 October 11- release vote opened ([VOTE] Release Apache TVM v0.10.0.rc0  #13026)
  • Bump up TVM version on main: Update to 0.11.dev0 #13036
  • [RESULT][VOTE]Release Apache TVM v0.10.0.rc0 #13101
• October 11 October 17- release published

Keep in mind this schedule is tentative and may change as we progress through the process.

A new issue will be made shortly before release vote detailing the release notes: #12979

cc @driazati @areusch @leandron

[vinx13]

would be great to have 7aef584 cherry-picked

[areusch]

I'm hoping to land #12880 shortly, will update this thread when it does so we can cherry-pick it.

[areusch]

#12880 is ready to cherry-pick

[areusch]

if it's not too late, could #12856 get cherry-picked as well?

[zhyncs]

@Hzfengsy @YuchenJin Hi TVM genius, when will relax be merged to tvm main upstream?

[Hzfengsy]

@zhyncs Thanks for your interest. Relax is at the RFC stage (apache/tvm-rfcs#89). And we will upstream it when the RFC passes.

[Johnson9009]

Does the release do more extra testing than the branch main?
In general, the release process contains two kinds of works, the first one is arrangement, like we have done here, e.g, release note, license confirmation, ..., the other one is testing, some company or organization may use the work "sign off", the full test suite will be confirmed to meet the release requirement.
My question is that do we have the extra "sign off" testing?
@AndrewZhaoLuo, @driazati, @tqchen Thanks.

[driazati]

Does the release do more extra testing than the branch main? In general, the release process contains two kinds of works, the first one is arrangement, like we have done here, e.g, release note, license confirmation, ..., the other one is testing, some company or organization may use the work "sign off", the full test suite will be confirmed to meet the release requirement. My question is that do we have the extra "sign off" testing? @AndrewZhaoLuo, @driazati, @tqchen Thanks.

Everything that we currently test is run on every commit, there is no 'official' special testing for a release beyond what was run on the last commit included in that release. IIUC the vote thread in #13026 is supposed to give interested users a time to run any tests of their own and voice related concerns if necessary.

[Johnson9009]

@driazati Understand, thanks.

[AndrewZhaoLuo]

Release done, thanks folks!