Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Doc]: Add latest / stable version after first final release #214

Open
Yikun opened this issue Mar 1, 2025 · 0 comments
Open

[Doc]: Add latest / stable version after first final release #214

Yikun opened this issue Mar 1, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@Yikun
Copy link
Collaborator

Yikun commented Mar 1, 2025 •
edited
Loading

📚 The doc issue

Bring some misleading here #211 (comment)

Suggest a potential alternative/fix

  1. latest --> the latest developer preview docs, link to main branch
  2. stable --> docs for the latest stable release, link to latest release tag
    seems stable release depends on a final release: https://docs.readthedocs.com/platform/stable/versions.html#versions-are-git-tags-and-branches
  3. Add a note like vllm latest doc: You are viewing the latest developer preview docs. Click here to view docs for the latest stable release.
Image
@Yikun Yikun added the documentation Improvements or additions to documentation label Mar 1, 2025
This was referenced Mar 1, 2025
Closed
Merged
wangxiyuan pushed a commit that referenced this issue Mar 3, 2025
@Yikun
Add Document Branch Policy (#217)
6e358c4 
### What this PR does / why we need it?
Add Document Branch Policy

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
CI passed

Related: #214

Signed-off-by: Yikun Jiang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Yikun