-
Notifications
You must be signed in to change notification settings - Fork 52
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
fix: Corrects release branch naming #333
Conversation
Signed-off-by: Daneyon Hansen <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danehans The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -34,7 +34,7 @@ This document defines the process for releasing Gateway API Inference Extension. | |||
export RC=1 | |||
``` | |||
|
|||
4. The vLLM image tag defaults to `0.7.2` for a release. Optionally, change the vLLM image tag. For example: | |||
4. The vLLM image tag defaults to `v0.7.2` for a release. Set the `VLLM` environment variable if a newer [tag][vllm-tag] has been published. For example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can we instead point to where the tag is defined? That would let us avoid having multiple sources of truth for this info
3. Create a new release branch from the `main` branch. The release branch should be named `release-v${MAJOR}.${MINOR}`, e.g. `release-v0.1`. | ||
3. Release Branch Handling: | ||
- For a Release Candidate: | ||
Create a new release branch from the `main` branch. The branch should be named `release-${MAJOR}.${MINOR}`, for example, `release-0.1`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Leaving a note mentioning that the patch version is intentionally left out may help.
Some examples of other folks making this mistake also:
https://github.com/kubernetes-sigs/lws/branches/stale
/lgtm LGTM! I left some ignorable nits, feel free to unhold and submit. |
/hold cancel I guess we can follow up with the suggestions separately |
VLLM
env var default value for the release doc.