chore: import upstream snapshot with attribution
This commit is contained in:
@@ -0,0 +1,11 @@
|
||||
You can post questions or issues or feedback through the following channels:
|
||||
|
||||
1. `Discussion Board`_: For **questions about Ray usage** or **feature requests**.
|
||||
2. `GitHub Issues`_: For **bug reports**.
|
||||
3. `Ray Slack`_: For **getting in touch** with Ray maintainers.
|
||||
4. `StackOverflow`_: Use the [ray] tag for **questions about Ray**.
|
||||
|
||||
.. _`Discussion Board`: https://discuss.ray.io/
|
||||
.. _`GitHub Issues`: https://github.com/ray-project/ray/issues
|
||||
.. _`Ray Slack`: https://www.ray.io/join-slack
|
||||
.. _`StackOverflow`: https://stackoverflow.com/questions/tagged/ray
|
||||
@@ -0,0 +1,6 @@
|
||||
.. admonition:: Check your version!
|
||||
|
||||
Things can change quickly, and so does this contributor guide.
|
||||
To make sure you've got the most cutting edge version of this guide,
|
||||
go check out the
|
||||
`latest version <https://docs.ray.io/en/master/ray-contribute/getting-involved.html>`__.
|
||||
@@ -0,0 +1,8 @@
|
||||
..
|
||||
.. note::
|
||||
|
||||
Ray 2.40 uses RLlib's new API stack by default.
|
||||
The Ray team has mostly completed transitioning algorithms, example scripts, and
|
||||
documentation to the new code base.
|
||||
|
||||
If you're still using the old API stack, see :doc:`New API stack migration guide </rllib/new-api-stack-migration-guide>` for details on how to migrate.
|
||||
Reference in New Issue
Block a user