[Release] v0.12.0 release schedule

[ysh329]

Although v0.11.0 released on Feb 25 and a relative bugfix minor version v0.11.1 released last month, relative PRs are all the last year November. This is unhealthy for our RFC-0067 about quarter-based releases, especially for AI infra companies which needs regularly merge with release version.

Consider v0.11.0 features are from last year Nov and quarter-based releases, I hope at the end of this month we can make a 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.12.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:

• 7 9 Apr 2023 - a branch v0.12.0 to be created from main
  • Done in https://github.com/apache/tvm/tree/v0.12.0
• 7 10 Apr 2023 - a tag v0.13.dev0 to be created, marking the beginning of the next development cycle
  • v0.13.0 points to 15f9be5
  • Done in https://github.com/apache/tvm/releases/tag/v0.13.dev0
• 13 Apr 2023 - 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
• 18 Apr 2023 - 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
• 22 18 Apr 2023 - Draft release notes published [Release] v0.12.0 Release Candidate Notes #14645
• 25 Apr 2023 5 May 2023 - release voting opens, [VOTE] Release Apache TVM v0.12.0.rc0 #14710
• 28 Apr 17 May 2023, delaying until mid May... - release date

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 @driazati @areusch @Mousius @tqchen @AndrewZhaoLuo

[Hzfengsy]

Thanks @ysh329 Happy to see volunteers for the quarterly. Please fix the following issue of the post

a tag v0.12.dev0 to be created, marking the beginning of the next development cycle

typo, should be v0.13.dev0

Note: for this specific release, given we'll have the end of the year period, I've extended the cherry-picking hard deadline in ~3 days, so that we some more time to consider patches to be included.

remove it

[ysh329]

Thanks @ysh329 Happy to see volunteers for the quarterly. Please fix the following issue of the post

a tag v0.12.dev0 to be created, marking the beginning of the next development cycle

typo, should be v0.13.dev0

Note: for this specific release, given we'll have the end of the year period, I've extended the cherry-picking hard deadline in ~3 days, so that we some more time to consider patches to be included.

remove it

Fixed. Thanks your reply.

[Johnson9009]

@ysh329 Thanks for bring this up, upgrade with official timely is good for the downstream companies, especially for companies like ARM China whose customers want to use the newest release version timely.

Thanks for excellent work of TVM community, ARM China built our heterogeneous execution product based on TVM, and learned a lot from community, so this quarter we will pay some time to help release the v0.12.0, @ysh329 is our team member, we will try our best to complete this release in Apr, so the downstream have more time to upgrade and resolve conflicts.

@tqchen @junrushao @AndrewZhaoLuo Please help to check if we release v0.12.0 at this time is ok? Thanks.

[areusch]

the timeline looks good to me, we do need someone to serve as release manager.

[tqchen]

Happy to help with some of the branch cutting works, Thanks @ysh329 for volunteering, would you be able to help release note drafting?

[ysh329]

Happy to help with some of the branch cutting works, Thanks @ysh329 for volunteering, would you be able to help release note drafting?

My pleasure. I'm recently preparing release note drafting. 😆

Please help create branch named v0.12.0 from main and v0.13.dev0 tag. @tqchen @Hzfengsy @junrushao

[Hzfengsy]

I helped create the v0.12.0 branch and will set the tag after the next commit merges. Could you please also send a PR to update the dev version like the commit #14241

[ysh329]

I helped create the v0.12.0 branch and will set the tag after the next commit merges. Could you please also send a PR to update the dev version like the commit #14241

Fixed. Please see #14544.

[xingyu-long]

Hi @ysh329, I am quite interested in being the release manager for this project. Do you have any requirements for it? And how can I get in touch with you or the team? Thanks!

[Hzfengsy]

@ysh329 tag v0.13dev0 created

[ysh329]

Hi @ysh329, I am quite interested in being the release manager for this project. Do you have any requirements for it? And how can I get in touch with you or the team? Thanks!

Thanks for your attention. We are already in the process of this release. Please feel free to raise your questions about release in this issue.

[tqchen]

#14571 needs to be cherry picked cc @Lunderberg