How to understand the verisoning policy between vllm and vllm-ascend?
Such as, vllm latest version (such as 0.8.0/0.8.1) that has just been released based on main branch. Does vllm-ascend supported it?
TL;DR
- We have a main to main CI[1] for vllm and vllm-ascend, if you want to use main vLLM branch (latset version vllm), please use the main branch doc (build from source)[2]
- As shown [4], note that vllm-ascend will only be released for a certain vLLM release version rather than all versions. Hence, You might see only part of versions have dev branches (such as only
0.7.1-dev/0.7.3-devbut no0.7.2-dev). - (20250325) we didn’t have a 0.8.x branch yet, but in short future we will make a branch like 0.8.x-dev
[1] vllm-ascend/.github/workflows/vllm_ascend_test.yaml at 3fb3b5cf75811ca66f60285b070de1ca7e0dc88b · vllm-project/vllm-ascend · GitHub
[2] main branch installation: Installation — vllm-ascend
[3] For release: Versioning policy — vllm-ascend
[4] For branch: Versioning policy — vllm-ascend
Hello, Currently, I have Ascend 910B3 in openEuler OS. But I notice that in the document, it seems that the vllm Ascend doesn’t support the 910B3 yet. And I want to know whether you are currently working on the adaption for 910B3 or just plan to do it in the future?
The A2 series already supported, you can follow below link to install:
(2025.04.01) Currently, we are working on main branch.
Before vLLM v0.9.x comming or 530, we will create sevral vllm-ascend release tag:
| vLLM release tag | vllm-ascend branch | vllm-ascend release tag |
|---|---|---|
| 0.8.2 | main or 0.8.2-dev | 0.8.1rc1, 0.8.1rc2 |
| 0.8.3 | main or 0.8.3-dev | 0.8.2rc1 |
| 0.8.x (2-3 weeks before Q2) | 0.8.x-dev | 0.8.x (Q2, final release), 0.8.x.post1 (After Q2, post release),0.8.x.post2 (After Q2, post release) |