From e9fb895b10cef37ea634f4d4af71686b09ca9f20 Mon Sep 17 00:00:00 2001 From: LookAround0301 Date: Fri, 22 Aug 2025 08:53:12 +0800 Subject: [PATCH] [Doc] Add feature branch long_seq_optimization (#2477) ### What this PR does / why we need it? Add cp/sp feature branch - vLLM version: v0.10.0 - vLLM main: https://github.com/vllm-project/vllm/commit/0c6e40bbaa4707528286a1e7bf17c90c88a1d920 Signed-off-by: LookAround --- docs/source/community/versioning_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/community/versioning_policy.md b/docs/source/community/versioning_policy.md index 13c7ebc..0c1b6cf 100644 --- a/docs/source/community/versioning_policy.md +++ b/docs/source/community/versioning_policy.md @@ -88,7 +88,7 @@ Usually, each minor version of vLLM (such as 0.7) will correspond to a vLLM Asce | Branch | Status | RFC link | Merge plan | Mentor | |------------|--------------|---------------------------------------|------------|--------| - +|rfc/long_seq_optimization|Maintained|https://github.com/vllm-project/vllm/issues/22693|930|wangxiyuan| - Branch: The feature branch should be created with a prefix `rfc/` followed by the feature name, such as `rfc/feature-name`. - Status: The status of the feature branch is `Maintained` until it is merged into the main branch or deleted. - RFC link: The feature branch should be created with a corresponding RFC issue. The creation of a feature branch requires an RFC and approval from at least two maintainers.