Mark v0.7.1 as unmaintained and v0.7.3 as maintained (#139)

### What this PR does / why we need it?
Mark v0.7.1 as unmaintained and v0.7.3 as maintained:
vLLM released the v0.7.3 version:
https://github.com/vllm-project/vllm/releases/tag/v0.7.3 which include
serval commits:
- https://github.com/vllm-project/vllm/pull/12874
- https://github.com/vllm-project/vllm/pull/12432
- https://github.com/vllm-project/vllm/pull/13208

We'd better to bump the versions to v0.7.3.

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
Preview

Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
This commit is contained in:
Yikun Jiang
2025-02-21 22:41:44 +08:00
committed by GitHub
parent 72a43a61d8
commit d21b3be685
4 changed files with 32 additions and 17 deletions

View File

@@ -40,10 +40,12 @@ Note that vllm-ascend will only be released for a certain vLLM release version r
Usually, each minor version of vLLM (such as 0.7) will correspond to a vllm-ascend version branch and support its latest version (for example, we plan to support version 0.7.3) as following shown:
| Branch | Status | Note |
|-----------|------------|--------------------------------------|
| main | Maintained | CI commitment for vLLM main branch |
| v0.7.1-dev | Maintained | CI commitment for vLLM 0.7.1 version |
| Branch | Status | Note |
|------------|--------------|--------------------------------------|
| main | Maintained | CI commitment for vLLM main branch |
| v0.7.3-dev | Maintained | CI commitment for vLLM 0.7.3 version |
| v0.7.1-dev | Unmaintained | Replaced by v0.7.3-dev |
## Release Compatibility Matrix
@@ -57,8 +59,7 @@ Following is the Release Compatibility Matrix for vLLM Ascend Plugin:
### Next final release (`v0.7.x`) window
| Date | Event |
|---------|-----------|
| February 2025 | Release candidates (RC1), v0.7.1rc1 |
| March 2025 | Release candidates (RC2), v0.7.1rc2 or v0.7.3rc1 |
| Date | Event |
|------------|------------------------------------------------------------------|
| March 2025 | Release candidates, v0.7.3rc1 |
| March 2025 | Final release passes, match vLLM v0.7.x latest: v0.7.1 or v0.7.3 |

View File

@@ -40,10 +40,11 @@ vllm-ascend有主干和开发两种分支。
通常来说vLLM每个minor版本比如0.7均会对应一个vllm-ascend版本分支并支持其最新的版本例如我们计划支持0.7.3版本)。如下所示:
| 分支 | 状态 | 备注 |
|-----------|------------|--------------------------------------|
| main | Maintained | 基于vLLM main分支CI看护 |
| v0.7.1-dev | Maintained | 基于vLLM 0.7.1版本CI看护 |
| 分支 | 状态 | 备注 |
|------------|--------------|---------------------|
| main | Maintained | 基于vLLM main分支CI看护 |
| v0.7.3-dev | Maintained | 基于vLLM v0.7.3版本CI看护 |
| v0.7.1-dev | Unmaintained | 被v0.7.3-dev分支代替 |
## 版本配套
@@ -57,8 +58,7 @@ vLLM Ascend Plugin (`vllm-ascend`) 的关键配套关系如下:
### 下一个正式版(`v0.7.x`)发布窗口
| 时间 | 事件 |
|------------|-----------------------------------|
| 2025年02月 | RC版本RC1, v0.7.1rc1 |
| 2025年03月 | RC版本RC2, v0.7.1rc2 or v0.7.3rc1 |
| 2025年03月 | 正式版, 匹配0.7.x最新的vLLM版本: v0.7.1 or v0.7.3 |
| 时间 | 事件 |
|----------|-------------------------------|
| 2025年03月 | RC版本, v0.7.3rc1 |
| 2025年03月 | 正式版, 匹配0.7.3最新的vLLM版本: v0.7.3 |