vllm-project / vllm-project/production-stack
feature: unify naming of production-stack, vllm-stack and vllm-router
Open
Nobody has claimed this yet.
discussion
feature request
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 503
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 8
Description
Describe the feature
Today multiple names are used, e.g.,
- repo name: production-stack
- release: vllm-stack
- container: production-stack/router
- python package name: vlllm-router
It would be great to have consistent naming all over, e.g., vllm-router
Why do you need this feature?
Simplifies usage and avoid confusion with different names
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by auditing the names listed in the issue: the repository, the vllm-stack release tag, the production-stack/router container package, and the Python package name in setup.py. Define the vllm-router naming convention across these surfaces and verify that releases, container references, and package metadata use it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100