v0.5.2, v0.5.3, v0.6.0 Release Tracker about vllm

[simon-mo]

Hi @sasha0552,

Thank you for bring this up. For now, would you mind maintain this in your fork? There are few reasons that we are hesitant to include support for Pascals:

• Aside from Triton, we are continuously relying on Cutlass, FlashAttention, and FlashInfer which all seems to dropped Pascal.
• It is sufficiently easy to build from source in vLLM with Pascal support.
• As we add more features and performance optimizations, we are afraid we can no longer test and maintain the support for support for Pascal due to added complexity.

[sasha0552]

Hello. Can #4409 be included in any of the next releases? Or at least, can I get an explanation as to why it can't be included (maybe I can help in some way?).

Once the wheel size limit increase was approved, and #6394 was merged, wheel size should not be an issue.

I am currently waiting for PyPI staff to approve the wheel size limit increase request to publish the patched triton to PyPI (pypi/support#4295).

It would be nice to see support for Pascal GPUs in vLLM. Many people use them because they are cheap.

[WoosukKwon]

July 23rd is Tuesday. Do you mean July 24th?

[AlphaINF]

hello, when will v0.6.0 release? I'm looking forward to #5036 and MiniCPM-Llama3-V-2_5

[simon-mo]

v0.5.2 has been released: https://github.com/vllm-project/vllm/releases/tag/v0.5.2

[AlphaINF]

Can this PR be added in v0.5.3?
#5036

[simon-mo]

@AlphaINF unlikely given the current state of the PR at the moment (still being reviewed). but I'm looking very much forward to this PR as well!

[AlphaINF]

@simon-mo thanks!

[bohr]

@simon-mo for this "async scheduling to overlap scheduling" do we have a plan？

[vrdn-23]

Would it be possible to get #6594 merged in before the next release is due? @joerunde @Yard1