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.

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

Outdated docs #51703

Open
JonDum opened this issue Mar 26, 2025 · 0 comments
Open

Outdated docs #51703

JonDum opened this issue Mar 26, 2025 · 0 comments
Labels
docs An issue or change related to documentation triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@JonDum
Copy link
Contributor

JonDum commented Mar 26, 2025

Description

I'm a new user to Ray and I've been engorging myself through the documentation.

I seem to have discovered Ray at an inopportune time because I'm finding a tremendous amount of examples and documentation that is out of date with the new api stack and it has been quite the journey digging through source code in order to determine what is and is not current, but I feel like I'm finally starting to get a hang of it.

That said, would maintainers find it useful if I document and maintain a list here when I come across an outdated example or documentation page? Or do you all have a good grasp on that internally.

Link

No response

@JonDum JonDum added docs An issue or change related to documentation triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Mar 26, 2025
@JonDum JonDum changed the title [<Ray component: Core|RLlib|etc...>] Outdated docs Outdated docs Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs An issue or change related to documentation triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

1 participant