Open simon-mo opened 4 months ago
This issue has been automatically marked as stale because it has not had any activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. Leave a comment if you feel this issue should remain open. Thank you!
Motivation.
Currently, vLLM manages the release and development version all through the main branch:
vllm.__version__ = A
while A is the current public version being releasedvllm.__version__ = B
.It presents some challenges
Proposed Change.
I think this RFC is open for suggestions.
One straw man proposal is as follows, which roughly follows the way in
ray-project/ray
:v0.k+1.0.dev0
wherek
is the current minor versionv0.k.j
, creates the tag and cherry-pick any hot fixes.The downside of this approach is the cumbersomeness of cherry-picks. But the upside is the ease of version management.
Feedback Period.
Open until concensus
CC List.
@WoosukKwon @robertgshaw2-neuralmagic @khluu @dgoupil @lanking520
Any Other Things.
No response