Skip to content

[Docs] Propose a deprecation policy for the project #17063

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

russellb
Copy link
Member

@russellb russellb commented Apr 23, 2025

vLLM has deprecated some features, though we lack a formal policy for
how and when we will deprecate features and eventually remove them.
This document includes a proposed process for that.

Signed-off-by: Russell Bryant [email protected]

Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

@mergify mergify bot added the documentation Improvements or additions to documentation label Apr 23, 2025
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR proposes an official deprecation policy for the project to clearly document the process for deprecating and eventually removing features from vLLM. Key changes include:

  • Adding a reference to the deprecation policy in the main documentation index.
  • Updating the metrics design document to link to the deprecation policy.
  • Introducing a new document outlining the deprecation pipeline, guidelines, and example timeline.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
docs/source/index.md Added a link to the deprecation policy in the contributing section.
docs/source/design/v1/metrics.md Inserted a reference to the deprecation policy in the metrics documentation.
docs/source/contributing/deprecation_policy.md New document detailing the deprecation process and timeline.

vLLM has deprecated some features, though we lack a formal policy for
how and when we will deprecate features and eventually remove this.
This document includes a proposed process for that.

Signed-off-by: Russell Bryant <[email protected]>
@russellb russellb force-pushed the deprecation-policy branch from 3629df5 to f6b7d20 Compare April 23, 2025 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants