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

Features Discussion before Next Release v0.18.0 #17391

Open
ysh329 opened this issue Sep 19, 2024 · 0 comments
Open

Features Discussion before Next Release v0.18.0 #17391

ysh329 opened this issue Sep 19, 2024 · 0 comments

Comments

@ysh329
Copy link
Contributor

ysh329 commented Sep 19, 2024

Hi all, based on our quarterly release schedule, next release is coming on Oct. The next release is vital for downstream companies, especially depended on TVM, whatever software or hardware companies.

Enable those software or hardware companies to have ability using large language model. Advance the democratization of AI.

Thus, it's necessary to discuss required features like v0.16.0 discussion (#16719):

  • New features. Will be the highlight of next release, attracting downstream companies or users.
    • New features without risks need to be highlighted.
    • Whether there are features that must be entered, but this time there may be risks. Do we need to delay time for this feature?
  • Bugs.
    • Should be considered, especially those obstacle new and core features.

I hope we can list required highlight features (with or without risks) and bugs needed to be fixed before release schedule begin.

@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 19, 2024
@ysh329 ysh329 pinned this issue Sep 20, 2024
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