Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Release] v0.18.0 release schedule #17412

Open
14 of 17 tasks
ysh329 opened this issue Sep 24, 2024 · 1 comment
Open
14 of 17 tasks

[Release] v0.18.0 release schedule #17412

ysh329 opened this issue Sep 24, 2024 · 1 comment

Comments

@ysh329
Copy link
Contributor

ysh329 commented Sep 24, 2024

Last release v0.17.0 was proposed at the end of July. and the release day is 25 July, more detail refer v0.17.0 release schedule. It has been almost three months since July. According to our RFC-0067 about quarter-based releases, I hope to release v0.18.0 version at the end of Oct 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.18.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 @Hzfengsy @vinx13 @areusch @Mousius @tqchen @AndrewZhaoLuo @Johnson9009

@ysh329 ysh329 added type: bug needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it and removed type: bug needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it labels Sep 24, 2024
@ysh329 ysh329 pinned this issue Sep 24, 2024
@ysh329
Copy link
Contributor Author

ysh329 commented Oct 11, 2024

This time has some difference from previous about version number files. According to git blame, I found there's a file named web/package-lock.json having version number, detailed see this link: #17420.

This mean each time release in future, this file web/package-lock.json needs change version number, too. #17461

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant