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

Prepare for release v0.6.0 #425

Open
6 of 10 tasks
kerthcet opened this issue Mar 11, 2025 · 9 comments
Open
6 of 10 tasks

Prepare for release v0.6.0 #425

kerthcet opened this issue Mar 11, 2025 · 9 comments

Comments

@kerthcet
Copy link
Contributor Author

cc @ahg-g @Edwinhr716 thoughts?

@kerthcet kerthcet pinned this issue Mar 11, 2025
@Edwinhr716
Copy link
Contributor

#386

Not sure if we should include this as part of the release. Not really anything to do from our side, more of a dependency that we have on vLLM.

@kerthcet
Copy link
Contributor Author

Make it part of the Glad to Have in case they won't publish new release this month.

@zhaizhch
Copy link

#388
I believe this feature is not only a critical necessity but also a highly trending topic in the current landscape. I strongly recommend prioritizing its development and releasing it as soon as possible.

@kerthcet
Copy link
Contributor Author

@zhaizhch consider we're close the the deadline of this release, we may not include it in this release, will consider it for next one.

@JesseStutler
Copy link

JesseStutler commented Mar 17, 2025

For #407, I will have time to write a proposal for everyone to review in April, so it seems I won't make it in time in March. Generally, lws releases a new version every 3 months? It looks like my feature will have to wait for the next version

@kerthcet
Copy link
Contributor Author

For #407, I will have time to write a proposal for everyone to review in April, so it seems I won't make it in time in March. Generally, lws releases a new version every 3 months? It looks like my feature will have to wait for the next version

Let's wait for the next release, we'll cut off this week.

@kerthcet
Copy link
Contributor Author

leave #400 to next release since it's only related to gang requirements right now.

@Edwinhr716
Copy link
Contributor

Can we close this issue @kerthcet?

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

4 participants