[Release] v0.13.0 release schedule #15134

ysh329 · 2023-06-21T12:20:51Z

Although last released v0.12.0 is on 17 May, the date of v0.12.0 branch cutting is 9 Apr. In other words, the v0.12.0 release is based on main branch of 9 Apr. It has been almost three months since April 9th.
According to our RFC-0067 about quarter-based releases, I hope to release v0.13.0 version in mid July. 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.13.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:

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

The text was updated successfully, but these errors were encountered:

tqchen · 2023-06-21T14:06:25Z

Happy to help with some of the branch cutting works, Thanks @ysh329 for volunteering

Hzfengsy · 2023-06-21T14:15:27Z

Thanks @ysh329. Happy to help with things that need permissions!

spectrometerHBH · 2023-06-23T18:27:19Z

I volunteer to help manage the release

Johnson9009 · 2023-06-26T10:15:52Z

Can below two steps be merged into one? Because these steps have some relationship, i.e., the commit of "v0.14.dev0" must be the next commit of branch v0.13.0, in addition these two steps can be done quickly as long as the contributor has enough permission.

1 July 2023 - a branch v0.13.0 to be created from main
3 July 2023 - a tag v0.14.dev0 to be created, marking the beginning of the next development cycle

In addition, there need add another step for modifying the version recorded in main branch code to "v0.14.dev0", because this step need to send a PR and need run all tests, so it maybe need 1~2 days to be merged.

ysh329 · 2023-06-26T14:49:11Z

Can below two steps be merged into one? Because these steps have some relationship, i.e., the commit of "v0.14.dev0" must be the next commit of branch v0.13.0, in addition these two steps can be done quickly as long as the contributor has enough permission.

1 July 2023 - a branch v0.13.0 to be created from main
3 July 2023 - a tag v0.14.dev0 to be created, marking the beginning of the next development cycle

In addition, there need add another step for modifying the version recorded in main branch code to "v0.14.dev0", because this step need to send a PR and need run all tests, so it maybe need 1~2 days to be merged.

Good question. I checked recently commit history records about 0.xx.dev0 on main branch and found the next submission of tagged 0.xx.dev0 were not PR changed version, which were non-standard.

I think these two things about a branch v0.13.0 to be created from main and a tag v0.14.dev0 to be created can be merged. Of course, the next submission of tagged 0.xx.dev0 should be the PR modifying the version recorded like this.

I modified the schedule and add a step about modifying the version recorded in main branch code to "v0.14.dev0". Besides, I add an item about modifying the version recorded in branch v0.13.0 like this.

ysh329 · 2023-07-01T08:32:20Z

Please help create branch named v0.13.0 from main and v0.14.dev0 tag. @tqchen @Hzfengsy

spectrometerHBH · 2023-07-02T17:49:17Z

Please help create branch named v0.13.0 from main and v0.14.dev0 tag. @tqchen @Hzfengsy

The new branch and tag is now ready.

ysh329 · 2023-07-03T02:31:45Z

I commit a PR about modifying the version recorded to v0.14.dev0 on main branch: #15208.

Hi @spectrometerHBH, please make a PR on v0.13.0 branch like this, modify version to 0.13.0 on v0.13.0 branch.

spectrometerHBH · 2023-07-03T21:17:06Z

@ysh329 cc: #15216

ysh329 · 2023-07-06T03:26:05Z

Hi all, this PR #15216 about modifying the version recorded to v0.13.0 on v0.13.0 branch is blocked by CI, but this won't block our cherry-picking soft deadline and cherry-picking hard deadline.

cc @driazati

ysh329 · 2023-07-06T08:15:06Z

Hi all, this PR #15216 about modifying the version recorded to v0.13.0 on v0.13.0 branch is blocked by CI, but this won't block our cherry-picking soft deadline and cherry-picking hard deadline.

cc @driazati

Can anybody help to see the CI issue? It seems these thing block the process of release schedule several times.

ysh329 · 2023-07-08T15:35:25Z

Hi all, this PR #15216 about modifying the version recorded to v0.13.0 on v0.13.0 branch is blocked by CI, but this won't block our cherry-picking soft deadline and cherry-picking hard deadline.
cc @driazati

Can anybody help to see the CI issue? It seems these thing block the process of release schedule several times.

Hi all, this Jenkins CI issue is about our Jenkins config for those non-main branchs will merge with latest main when CI running, this has no relation with Github branch protection.

Besides, this CI issue exposes our release step about version modification having some latent problem. We should modify version to 0.13.0 on main branch first and then do v0.13.0 branch cutting from main.:

First, modify version to 0.13.0 on main branch first can avoid Jenkins CI conflict on Github between main and non-main branch, especially for one file in two branch existing divergence;
Second, downstream companies codes are regulary git merge with release branch. If release version number modification is introduced on main, downstream companies can avoid locally conflicts about version number when git merge this release branch codes based on last release branch codes.

tqchen · 2023-07-08T16:37:42Z

I think the issue is that the PR always assumes merge with main in that Jenkinsfile

ysh329 · 2023-07-09T11:02:37Z

Hi all, this PR #15216 about modifying the version recorded to v0.13.0 on v0.13.0 branch is blocked by CI, but this won't block our cherry-picking soft deadline and cherry-picking hard deadline.
cc @driazati

Can anybody help to see the CI issue? It seems these thing block the process of release schedule several times.

Hi all, this Jenkins CI issue is about our Jenkins config for those non-main branchs will merge with latest main when CI running, this has no relation with Github branch protection.

Besides, this CI issue exposes our release step about version modification having some latent problem. We should modify version to 0.13.0 on main branch first and then do v0.13.0 branch cutting from main.:

First, modify version to 0.13.0 on main branch first can avoid Jenkins CI conflict on Github between main and non-main branch, especially for one file in two branch existing divergence;

Second, downstream companies codes are regulary git merge with release branch. If release version number modification is introduced on main, downstream companies can avoid locally conflicts about version number when git merge this release branch codes based on last release branch codes.

I think branch protection is no problem, because the git merge operation is actually a protection mechanism for our publishing branch. Fundamentally, ensure that the PR introduced by the release branch is in the form of Cherry Pick on the main branch. And in theory, as long as the PR of cherry pick is in order introduced from main, there will be no conflicts on the publishing branch.

The behavior of version modification on release branch was not in the form of Cherry Pick, and after branch cutting, we made changes on the main branch, which caused divergence thus conflicts. I think we can first modify the version number on the main branch next time, because two reason as above.

ysh329 · 2023-07-11T14:50:07Z

Hi all, considering the originally scheduled voting day is a weekend, I'll advance voting day to this Friday (07/14/2023). Thus we need prepare release candidate packaging and uploading in advance.

cc @Hzfengsy

ysh329 · 2023-07-12T02:53:29Z

Hi all, v0.13.0 Release Candidate Notes published in advance: #15295

ysh329 · 2023-07-13T15:24:45Z

Please help prepare release candidate packaging and uploading for voting.

cc @Hzfengsy @junrushao @tqchen

ysh329 · 2023-07-14T02:21:54Z

Please help prepare release candidate packaging and uploading for voting.

cc @Hzfengsy @junrushao @tqchen

Please help delete branch v0.13.0-rc, rc-v0.13.0, and prepare candidate packaging for branch v0.13.0.

Hzfengsy · 2023-07-14T02:41:36Z

@ysh329 packages are ready now.

ysh329 · 2023-07-14T05:36:45Z

@ysh329 packages are ready now.

I tested v0.13.0.rc0 and passed.

Check sha512

# Check sha512
$ shasum -a 512 ./apache-tvm-src-v0.13.0.rc0.tar.gz
da0fa8ad9a858b297fc1dc883a37505f6277e57568e9770a734b99ad34379d4bde6f7fde0d93a7ebf2454dd2086d9c1567e3768cd55bc50ca9749762628b89c0  ./apache-tvm-src-v0.13.0.rc0.tar.gz
$ cat ./apache-tvm-src-v0.13.0.rc0.tar.gz.sha512
da0fa8ad9a858b297fc1dc883a37505f6277e57568e9770a734b99ad34379d4bde6f7fde0d93a7ebf2454dd2086d9c1567e3768cd55bc50ca9749762628b89c0  apache-tvm-src-v0.13.0.rc0.tar.gz

Check asc

# Check asc
$ gpg --import ./KEYS
gpg: key 6754EA97C55E3DEB: "Tianqi Chen (CODE SIGNING KEY) <[email protected]>" not changed
gpg: key 8955D84E20C9AB0C: "Yizhi Liu <[email protected]>" not changed
gpg: key 3A709F6F2B86E9D6: "Yizhi Liu (Yizhi Liu at Apache) <[email protected]>" not changed
gpg: key CA751254E97B9FE4: "Yizhi Liu <[email protected]>" not changed
gpg: key ED03B26E4FC3509F: "Ziheng Jiang <[email protected]>" not changed
gpg: key 9FBECBD3D75EFD4B: "Zhi Chen <[email protected]>" not changed
gpg: key 35ABC9676004ADAE: "Junru Shao <[email protected]>" not changed
gpg: key 2C75E5A496C80880: "Wuwei Lin <[email protected]>" not changed
gpg: key 07FA463F1C926F48: "David Riazati <[email protected]>" not changed
gpg: key C9A56ABD5CCA3EB8: "Andrew Zhao Luo <[email protected]>" not changed
gpg: key 28D4862222B8EC31: "Leandro Nunes <[email protected]>" not changed
gpg: key 06D051CA84EF3749: public key "Siyuan Feng (CODE SIGNING KEY) <[email protected]>" imported
gpg: Total number processed: 12
gpg:               imported: 1
gpg:              unchanged: 11
$ gpg --verify ./apache-tvm-src-v0.13.0.rc0.tar.gz.asc ./apache-tvm-src-v0.13.0.rc0.tar.gz
gpg: Signature made Fri Jul 14 10:24:35 2023 CST
gpg:                using RSA key 664EF29634C05669C3DCF83106D051CA84EF3749
gpg: Good signature from "Siyuan Feng (CODE SIGNING KEY) <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 664E F296 34C0 5669 C3DC  F831 06D0 51CA 84EF 3749

$ gpg --edit-key 664EF29634C05669C3DCF83106D051CA84EF3749
gpg> trust
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y

$ gpg --verify ./apache-tvm-src-v0.13.0.rc0.tar.gz.asc ./apache-tvm-src-v0.13.0.rc0.tar.gz
gpg: Signature made Fri Jul 14 10:24:35 2023 CST
gpg:                using RSA key 664EF29634C05669C3DCF83106D051CA84EF3749
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   3  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 3u
gpg: next trustdb check due at 2025-04-22
gpg: Good signature from "Siyuan Feng (CODE SIGNING KEY) <[email protected]>" [ultimate]

Check binary

# check binary
$ find ./apache-tvm-src-v0.13.0 -type f -exec file {} + | grep -w "ELF\|shared object"
# find nothing

Compile and Python Import on Linux

Passed with default config.

ysh329 · 2023-07-14T06:32:47Z

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

ysh329 · 2023-07-21T07:25:45Z

Hi all, vote passes with #14844, next we'll upload the binaries to Apache mirrors and create a new release TAG named v0.13.0 meanwhile remove the pre-release candidate TAG v0.13.0.rc0. This program needs help please.

Besides, we need update doc website too. According to last release talk as below, this step would need ASF perm.

@ysh329 Thanks for spotting this. The download page is broken now, it only includes links for v0.8 release. This is because previous PRs to tvm-site wasn't send to main branch, so manual rebuild of the site will overwrite the contents.
The update of the site should follow steps: 1) send PR to tvm-site/main to update download links and run scripts/task_deploy_asf_site.sh 2) push docs to asf-site branch

Originally posted by @vinx13 in #14505 (comment)

cc @Hzfengsy @junrushao @vinx13 @tqchen

ysh329 · 2023-07-26T09:56:02Z

Hi all, vote passes with #14844, next we'll upload the binaries to Apache mirrors and create a new release TAG named v0.13.0 meanwhile remove the pre-release candidate TAG v0.13.0.rc0. This program needs help please.

Besides, we need update doc website too. According to last release talk as below, this step would need ASF perm.

@ysh329 Thanks for spotting this. The download page is broken now, it only includes links for v0.8 release. This is because previous PRs to tvm-site wasn't send to main branch, so manual rebuild of the site will overwrite the contents.
The update of the site should follow steps: 1) send PR to tvm-site/main to update download links and run scripts/task_deploy_asf_site.sh 2) push docs to asf-site branch

Originally posted by @vinx13 in #14505 (comment)

cc @Hzfengsy @junrushao @vinx13 @tqchen

Hi all, let's persevere until the end. The sight of a great triumph is coming soon. cc @Hzfengsy @junrushao @vinx13 @tqchen

Hzfengsy · 2023-07-26T11:15:55Z

I have Updated Github pre_release to release and also upload to the svn release folder

ysh329 · 2023-08-02T04:53:58Z

Hi all, vote passes with #14844, next we'll upload the binaries to Apache mirrors and create a new release TAG named v0.13.0 meanwhile remove the pre-release candidate TAG v0.13.0.rc0. This program needs help please.
Besides, we need update doc website too. According to last release talk as below, this step would need ASF perm.

@ysh329 Thanks for spotting this. The download page is broken now, it only includes links for v0.8 release. This is because previous PRs to tvm-site wasn't send to main branch, so manual rebuild of the site will overwrite the contents.
The update of the site should follow steps: 1) send PR to tvm-site/main to update download links and run scripts/task_deploy_asf_site.sh 2) push docs to asf-site branch

Originally posted by @vinx13 in #14505 (comment)
cc @Hzfengsy @junrushao @vinx13 @tqchen

Hi all, let's persevere until the end. The sight of a great triumph is coming soon. cc @Hzfengsy @junrushao @vinx13 @tqchen

Hi @vinx13 , can you help update docs to website?

vinx13 · 2023-08-08T19:28:03Z

I've updated the website

ysh329 added needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it type: bug labels Jun 21, 2023

ysh329 mentioned this issue Jul 14, 2023

[VOTE] Release Apache TVM v0.13.0.rc0 #15313

Closed

ysh329 mentioned this issue Jul 21, 2023

[RESULT] [VOTE] Release Apache TVM v0.13.0 #15376

Closed

vinx13 closed this as completed Aug 8, 2023

ysh329 mentioned this issue Sep 24, 2023

[Release] v0.14.0 release schedule #15812

Closed

18 tasks

ysh329 mentioned this issue Dec 26, 2023

[Release] v0.15.0 release schedule #16277

Open

17 tasks

ysh329 mentioned this issue Apr 9, 2024

[Release] v0.16.0 release schedule #16857

Open

17 tasks

ysh329 mentioned this issue Jun 27, 2024

[Release] v0.17.0 release schedule #17122

Open

17 tasks

ysh329 mentioned this issue Sep 24, 2024

[Release] v0.18.0 release schedule #17412

Open

17 tasks

ysh329 mentioned this issue Dec 27, 2024

[Release] v0.19.0 release schedule #17575

Open

17 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Release] v0.13.0 release schedule #15134

[Release] v0.13.0 release schedule #15134

ysh329 commented Jun 21, 2023 •

edited by vinx13

Loading

tqchen commented Jun 21, 2023

Hzfengsy commented Jun 21, 2023

spectrometerHBH commented Jun 23, 2023

Johnson9009 commented Jun 26, 2023

ysh329 commented Jun 26, 2023 •

edited

Loading

ysh329 commented Jul 1, 2023

spectrometerHBH commented Jul 2, 2023 •

edited

Loading

ysh329 commented Jul 3, 2023 •

edited

Loading

spectrometerHBH commented Jul 3, 2023

ysh329 commented Jul 6, 2023 •

edited

Loading

ysh329 commented Jul 6, 2023

ysh329 commented Jul 8, 2023 •

edited

Loading

tqchen commented Jul 8, 2023

ysh329 commented Jul 9, 2023 •

edited

Loading

ysh329 commented Jul 11, 2023 •

edited

Loading

ysh329 commented Jul 12, 2023

ysh329 commented Jul 13, 2023

ysh329 commented Jul 14, 2023

Hzfengsy commented Jul 14, 2023

ysh329 commented Jul 14, 2023 •

edited

Loading

ysh329 commented Jul 14, 2023

ysh329 commented Jul 21, 2023 •

edited

Loading

ysh329 commented Jul 26, 2023

Hzfengsy commented Jul 26, 2023

ysh329 commented Aug 2, 2023

vinx13 commented Aug 8, 2023

[Release] v0.13.0 release schedule #15134

[Release] v0.13.0 release schedule #15134

Comments

ysh329 commented Jun 21, 2023 • edited by vinx13 Loading

tqchen commented Jun 21, 2023

Hzfengsy commented Jun 21, 2023

spectrometerHBH commented Jun 23, 2023

Johnson9009 commented Jun 26, 2023

ysh329 commented Jun 26, 2023 • edited Loading

ysh329 commented Jul 1, 2023

spectrometerHBH commented Jul 2, 2023 • edited Loading

ysh329 commented Jul 3, 2023 • edited Loading

spectrometerHBH commented Jul 3, 2023

ysh329 commented Jul 6, 2023 • edited Loading

ysh329 commented Jul 6, 2023

ysh329 commented Jul 8, 2023 • edited Loading

tqchen commented Jul 8, 2023

ysh329 commented Jul 9, 2023 • edited Loading

ysh329 commented Jul 11, 2023 • edited Loading

ysh329 commented Jul 12, 2023

ysh329 commented Jul 13, 2023

ysh329 commented Jul 14, 2023

Hzfengsy commented Jul 14, 2023

ysh329 commented Jul 14, 2023 • edited Loading

Check sha512

Check asc

Check binary

Compile and Python Import on Linux

ysh329 commented Jul 14, 2023

ysh329 commented Jul 21, 2023 • edited Loading

ysh329 commented Jul 26, 2023

Hzfengsy commented Jul 26, 2023

ysh329 commented Aug 2, 2023

vinx13 commented Aug 8, 2023

ysh329 commented Jun 21, 2023 •

edited by vinx13

Loading

ysh329 commented Jun 26, 2023 •

edited

Loading

spectrometerHBH commented Jul 2, 2023 •

edited

Loading

ysh329 commented Jul 3, 2023 •

edited

Loading

ysh329 commented Jul 6, 2023 •

edited

Loading

ysh329 commented Jul 8, 2023 •

edited

Loading

ysh329 commented Jul 9, 2023 •

edited

Loading

ysh329 commented Jul 11, 2023 •

edited

Loading

ysh329 commented Jul 14, 2023 •

edited

Loading

ysh329 commented Jul 21, 2023 •

edited

Loading