You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
changed the title
[<Ray component: Core|RLlib|etc...>] Outdated docs
Outdated docs
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
The text was updated successfully, but these errors were encountered: