[Release] v0.11.0 release schedule

[leandron]

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.11.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:

• 12 13 December 2022 - a branch v0.11.0 to be created from main
  • Done in https://github.com/apache/tvm/tree/v0.11.0
• 12 13 December 2022 - a tag v0.12.dev0 to be created, marking the beginning of the next development cycle
  • v0.12.0 points to 12311dc
  • https://github.com/apache/tvm/tree/v0.12.dev0
• 16 December 2022 - 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
• 04 06 January 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
• ~1 February 2023 - Draft release notes published - TVM v0.11.0 Release Candidate Notes #13899
• 25 February 2023 - release voting opens [VOTE] Release Apache TVM v0.11.0.rc0 #14129
• 2 March 2023 - release date https://github.com/apache/tvm/releases

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

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

[leandron]

@apache/tvm-committers Just a reminder that today is the last day to have fixes and PRs ported to the v0.11.0 branch. Let me know.

[areusch]

we discussed the release in the community meeting this morning. here are notes:

• release is running late. @leandron will update the schedule
• branch created, current status is past the hard deadline for cherry-picks. can still get a few last commits in given we are behind (but speak up soon).
• still need to put the release notes together, we have a script but it may need some edits (it can be tough to get prose from various parties to summarize the changes).
• note: tests/scripts/release script has mostly been tested on mac.
• if you want to try out the 0.11 prerelease wheel, it's built on pypi and you can try it with pip install --pre apache-tvm~=0.11. we will also upload the prerelease tarball before opening a vote thread.

[leandron]

I'm picking this up and facing an issue with protected branches when trying to cherry-pick #13624 into v0.11.0 - any idea how to solve that?

$ git push -f upstream v0.11.0
Enumerating objects: 42, done.
Counting objects: 100% (42/42), done.
Delta compression using up to 8 threads
Compressing objects: 100% (19/19), done.
Writing objects: 100% (23/23), 3.97 KiB | 1.32 MiB/s, done.
Total 23 (delta 18), reused 5 (delta 4), pack-reused 0
remote: Resolving deltas: 100% (18/18), completed with 18 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/v0.11.0.
remote: error: At least 1 approving review is required by reviewers with write access. Commits must have valid signatures.
To github.com:apache/tvm.git
 ! [remote rejected]     v0.11.0 -> v0.11.0 (protected branch hook declined)
error: failed to push some refs to 'github.com:apache/tvm.git'

$ git push --delete upstream v0.11.0
remote: error: GH006: Protected branch update failed for refs/heads/v0.11.0.
remote: error: Cannot delete this protected branch
To github.com:apache/tvm.git
 ! [remote rejected]     v0.11.0 (protected branch hook declined)
error: failed to push some refs to 'github.com:apache/tvm.git'

cc @driazati

[driazati]

The release branches are protected from force pushes / deletes by GitHub, but cherry-picking shouldn't require rewriting history right? Are you doing something like this?

git fetch origin
git checkout v0.11.0
git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e
git push origin

[Johnson9009]

Can we ensure a date that this release will be completed? So the downstream organization can decide whether sync this release to our internal or not, thanks.

[leandron]

Can we ensure a date that this release will be completed? So the downstream organization can decide whether sync this release to our internal or not, thanks.

I'm working on this at the moment, and will update here as soon as it's ready for review/vote. thanks.

[leandron]

The release branches are protected from force pushes / deletes by GitHub, but cherry-picking shouldn't require rewriting history right? Are you doing something like this?

git fetch origin
git checkout v0.11.0
git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e
git push origin

I was just trying to produce the tarball with the actual v0.11.0 with that cherry-picked commit, but I'm probably missing something:

% git remote -v
origin	git@github.com:leandron/tvm.git (fetch)
origin	git@github.com:leandron/tvm.git (push)
upstream	git@github.com:apache/tvm.git (fetch)
upstream	git@github.com:apache/tvm.git (push)

% git fetch upstream
% git checkout upstream/v0.11.0

% git reset --hard upstream/v0.11.0                       
HEAD is now at 1d9863470 [TIR] Fix PlanAndUpdateBufferAllocationLocation not visiting constant buffer (#13605)

% git cherry-pick 0eabbac2160a8a630e1994969f664ccf6233fc7e
[v0.11.0 2f999d62e] [BugFix][UMA] Protect target registration (#13624)
 Author: Balint Cristian <cristian.balint@gmail.com>
 Date: Fri Dec 16 15:23:26 2022 +0200
 4 files changed, 42 insertions(+), 16 deletions(-)

% git push upstream v0.11.0                        
Enumerating objects: 42, done.
Counting objects: 100% (42/42), done.
Delta compression using up to 8 threads
Compressing objects: 100% (19/19), done.
Writing objects: 100% (23/23), 3.93 KiB | 3.93 MiB/s, done.
Total 23 (delta 18), reused 5 (delta 4), pack-reused 0
remote: Resolving deltas: 100% (18/18), completed with 18 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/v0.11.0.
remote: error: At least 1 approving review is required by reviewers with write access. Commits must have valid signatures.
To github.com:apache/tvm.git
 ! [remote rejected]     v0.11.0 -> v0.11.0 (protected branch hook declined)
error: failed to push some refs to 'github.com:apache/tvm.git'
% 

[manupak]

Looks like the GH branch protection is kicking in , kind of like : https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging

Alternatively, you could do a PR to the branch (and merge it)?

[areusch]

i have asked asf-infra whether perhaps gitbox has misconfigured our branch protection. i'm not able to view that natively in the GH UI, i believe, so i'm left to deduce what i can from the asf.yaml and associated docs.