diff --git a/doc/dev/RELEASE_PROCESS.rst b/doc/dev/RELEASE_PROCESS.rst
deleted file mode 100644
index b14a3ef4e..000000000
--- a/doc/dev/RELEASE_PROCESS.rst
+++ /dev/null
@@ -1,218 +0,0 @@
-Release Process
-===============
-
-This document describes the process for creating new releases.
-
-1. **Create a release branch:** Create the branch from the desired commit on master
-   In order to create the branch, locally checkout the commit ID i.e.,
-   ``git checkout <hash>``. Then checkout a new branch of the format
-   ``releases/<release-version>``. Then push that branch to the ray repo:
-   ``git push upstream releases/<release-version>``.
-
-2. **Update the release branch version:** Push a commit directly to the
-   newly-created release branch that increments the Python package version in
-   python/ray/__init__.py and src/ray/raylet/main.cc. See this
-   `sample commit for bumping the release branch version`_.
-
-3. **Update the master branch version:**
-
-   For a new minor release (e.g., 0.7.0): Create a pull request to
-   increment the dev version in of the master branch. See this
-   `sample PR for bumping a minor release version`_. **NOTE:** Not all of
-   the version numbers should be replaced. For example, ``0.7.0`` appears in
-   this file but should not be updated.
-
-   For a new micro release (e.g., 0.7.1): No action is required.
-
-4. **Testing:** Before releasing, the following sets of tests should be run.
-   The results of each of these tests for previous releases are checked in
-   under ``doc/dev/release_logs``, and should be compared against to identify
-   any regressions.
-
-   1. Long-running tests
-
-   .. code-block:: bash
-
-       ray/ci/long_running_tests/README.rst
-
-   Follow the instructions to kick off the tests and check the status of the workloads.
-   These tests should run for at least 24 hours without erroring or hanging (ensure that it is printing new iterations and CPU load is
-   stable in the AWS console).
-
-   2. Long-running multi-node tests
-
-   .. code-block:: bash
-
-      ray/ci/long_running_distributed_tests/README.rst
-
-   Follow the instructions to kick off the tests and check the status of the workloads.
-   These suite of tests are similar to the standard long running tests, except these actually run in a multi-node cluster instead of just a simulated one.
-   These tests should also run for at least 24 hours without erroring or hanging.
-
-   **IMPORTANT**: check that the test are actually running (printing output regularly) and aren't
-   just stuck at an iteration. You must also check that the node CPU usage is stable
-   (and not increasing or decreasing over time, which indicates a leak). You can see the head node
-   and worker node CPU utilizations in the AWS console.
-
-   3. Multi-node regression tests
-
-   Follow the same instruction as long running stress tests. The large scale distributed
-   regression tests identify potential performance regression in distributed environment.
-   The following test should be ran:
-
-   - ``ci/regression_test/rllib_regression-tests`` run the compact regression test for rllib.
-   - ``ci/regression_test/rllib_stress_tests`` run multinode 8hr IMPALA trial.
-   - ``ci/regression_test/stress_tests`` contains two tests: ``many_tasks`` and ``dead_actors``.
-     Each of the test runs on 105 spot instances.
-   - ``ci/regression_test/stress_tests/placement_group`` contains a Python script to run tests.
-     It currently uses ``cluster_util`` to emulate the cluster testing. It will be converted to 
-     real multi-node tests in the future. For now, just make sure the test succeed locally.
-
-   Make sure that these pass. For the RLlib regression tests, there shouldn't be any errors
-   and the rewards should be similar to previous releases. For the rest, it will be obvious if
-   they passed.  This will use the autoscaler to start a bunch of machines and run some tests.
-
-   **IMPORTANT**: You must get signoff from the RLlib team for the RLlib test results.
-
-   The summaries printed by each test should be checked in under
-   ``doc/dev/release_logs/<version>`` on the **master** branch (make a pull request).
-
-   4. Microbenchmarks
-
-   Run the ``ci/microbenchmark`` with the commit. Under the hood, the session will
-   run `ray microbenchmark` on an `m4.16xl` instance running `Ubuntu 18.04` with `Python 3`
-   to get the latest microbenchmark numbers.
-
-   The results should be checked in under ``doc/dev/release_logs/<version>``.
-
-   You can also get the performance change rate from the previous version using
-   microbenchmark_analysis.py
-
-   5. ASAN tests
-
-   Run the ``ci/asan_tests`` with the commit. This will enable ASAN build and run the
-   whole Python tests to detect memory leaks.
-
-5. **Resolve release-blockers:** If a release blocking issue arises, there are
-   two ways the issue can be resolved: 1) Fix the issue on the master branch and
-   cherry-pick the relevant commit  (using ``git cherry-pick``) onto the release
-   branch (recommended). 2) Revert the commit that introduced the bug on the
-   release branch (using ``git revert``), but not on the master (not recommended).
-
-   These changes should then be pushed directly to the release branch.
-
-6. **Create a GitHub release:** Create a `GitHub release`_. This should include
-   **release notes**. Copy the style and formatting used by previous releases.
-   Create a draft of the release notes containing information about substantial
-   changes/updates/bugfixes and their PR numbers. Once you have a draft, send it
-   out to other Ray developers (especially those who contributed heavily during
-   this release) for feedback. At the end of the release note, you should also
-   add a list of contributors. Make sure Ray, Tune, RLLib, Autoscaler are
-   capitalized correctly.
-
-   Run ``doc/dev/get_contributors.py`` to generate the list of commits corresponding
-   to this release and the formatted list of contributors.
-   You will need to provide a GitHub personal access token
-   (github.com -> settings -> developer settings -> personal access tokens).
-
-    .. code-block:: bash
-
-      # Must be run from inside the Ray repository.
-      pip install PyGitHub tqdm
-      python get_contributors.py --help
-      python get_contributors.py \
-        --access-token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
-        --prev-release-commit="<COMMIT_SHA>" \
-        --curr-release-commit="<COMMIT_SHA>"
-
-7. **Download all the wheels:** Now the release is ready to begin final
-   testing. The wheels are automatically uploaded to S3, even on the release
-   branch. To test, ``pip install`` from the following URLs:
-
-   .. code-block:: bash
-
-       export RAY_HASH=...  # e.g., 618147f57fb40368448da3b2fb4fd213828fa12b
-       export RAY_VERSION=...  # e.g., 0.7.0
-
-       # Linux Wheels
-       pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp36-cp36m-manylinux2014_x86_64.whl
-       pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp37-cp37m-manylinux2014_x86_64.whl
-       pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp38-cp38-manylinux2014_x86_64.whl
-
-       # Mac Wheels
-       pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp36-cp36m-macosx_10_13_intel.whl
-       pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp37-cp37m-macosx_10_13_intel.whl
-       pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp38-cp38-macosx_10_13_x86_64.whl
-
-   This can be tested if you use the script source ./bin/download_wheels.sh
-
-8. **Upload to PyPI Test:** Upload the wheels to the PyPI test site using
-   ``twine``.
-
-   .. code-block:: bash
-
-     # Downloads all of the wheels to the current directory.
-     RAY_VERSION=<version> RAY_HASH=<commit_sha> bash download_wheels.sh
-
-     # Will ask for your PyPI test credentials and require that you're a maintainer
-     # on PyPI test. If you are not, ask @robertnishihara to add you.
-     pip install twine
-     twine upload --repository-url https://test.pypi.org/legacy/ *.whl
-
-   Test that you can install the wheels with pip from the PyPI test repository:
-
-   .. code-block:: bash
-
-     # First install ray normally because installing from test.pypi.org won't
-     # be able to install some of the other dependencies.
-     pip install ray
-     pip uninstall ray
-
-     pip install --index-url https://test.pypi.org/simple/ ray
-
-   Then start Python, make sure you can ``import ray`` and run some simple Ray
-   scripts. Make sure that it is finding the version of Ray that you just
-   installed by checking ``ray.__version__`` and ``ray.__file__``.
-
-   Do this for MacOS, Linux, and Windows.
-
-   This process is automated. Run ./bin/pip_download_test.sh.
-   This will download the ray from the test pypi repository and run the minimum
-   sanity check from all the Python version supported. (3.6, 3.7, 3.8)
-
-   Windows sanity check test is currently not automated.
-
-9. **Upload to PyPI:** Now that you've tested the wheels on the PyPI test
-   repository, they can be uploaded to the main PyPI repository. Be careful,
-   **it will not be possible to modify wheels once you upload them**, so any
-   mistake will require a new release.
-
-   .. code-block:: bash
-
-     # Will ask for your real PyPI credentials and require that you're a maintainer
-     # on real PyPI. If you are not, ask @robertnishihara to add you.
-     twine upload --repository-url https://upload.pypi.org/legacy/ *.whl
-
-   Now, try installing from the real PyPI mirror. Verify that the correct version is
-   installed and that you can run some simple scripts.
-
-   .. code-block:: bash
-
-     pip install -U ray
-
-10. **Create a point release on readthedocs page:** Go to the `Ray Readthedocs version page`_.
-    Scroll to "Activate a version" and mark the *release branch* as "active" and "public". This creates a point release for the documentation.
-    Message @richardliaw to add you if you don't have access.
-
-11. **Update 'Default Branch' on the readthedocs page:** Go to the `Ray Readthedocs advanced settings page`_.
-    In 'Global Settings', set the 'Default Branch' to the *release branch*. This redirects the documentation to the latest pip release.
-    Message @richardliaw to add you if you don't have access.
-
-12. **Improve the release process:** Find some way to improve the release
-    process so that whoever manages the release next will have an easier time.
-
-.. _`sample PR for bumping a minor release version`: https://github.com/ray-project/ray/pull/6303
-.. _`sample commit for bumping the release branch version`: https://github.com/ray-project/ray/commit/a39325d818339970e51677708d5596f4b8f790ce
-.. _`GitHub release`: https://github.com/ray-project/ray/releases
-.. _`Ray Readthedocs version page`: https://readthedocs.org/projects/ray/versions/
-.. _`Ray Readthedocs advanced settings page`: https://readthedocs.org/dashboard/ray/advanced/
diff --git a/doc/dev/bin/ray-project/cluster.yaml b/doc/dev/bin/ray-project/cluster.yaml
deleted file mode 100644
index 14c8caf42..000000000
--- a/doc/dev/bin/ray-project/cluster.yaml
+++ /dev/null
@@ -1,38 +0,0 @@
-# This file is generated by `ray project create`.
-
-# A unique identifier for the head node and workers of this cluster.
-cluster_name: sanity-check
-
-# The maximum number of workers nodes to launch in addition to the head
-# node. This takes precedence over min_workers. min_workers defaults to 0.
-max_workers: 0
-
-# Cloud-provider specific configuration.
-provider:
-    type: aws
-    region: us-west-2
-    availability_zone: us-west-2a
-
-# How Ray will authenticate with newly launched nodes.
-auth:
-    ssh_user: ubuntu
-
-# Custom commands that will be run on the head node after common setup.
-head_setup_commands: 
-    # Install Anaconda.
-    - wget --quiet https://repo.continuum.io/archive/Anaconda3-5.0.1-Linux-x86_64.sh || true
-    - bash Anaconda3-5.0.1-Linux-x86_64.sh -b -p $HOME/anaconda3 || true
-    - echo 'export PATH="$HOME/anaconda3/bin:$PATH"' >> ~/.bashrc
-    - echo 'RAY_VERSION=0.8.7' >> ~/.bashrc
-    - echo 'RAY_HASH=56810e136587432ed4758d882bf8894b930355e3' >> ~/.bashrc
-    - chmod +x ./pip_download_test.sh || true
-    - pip install -U pip 
-
-# Custom commands that will be run on worker nodes after common setup.
-worker_setup_commands: []
-
-# Command to start ray on the head node. You don't need to change this.
-head_start_ray_commands: [ray stop]
-
-# Command to start ray on worker nodes. You don't need to change this.
-worker_start_ray_commands: [ray stop]
\ No newline at end of file
diff --git a/doc/dev/bin/ray-project/project.yaml b/doc/dev/bin/ray-project/project.yaml
deleted file mode 100644
index 41f488fe5..000000000
--- a/doc/dev/bin/ray-project/project.yaml
+++ /dev/null
@@ -1,36 +0,0 @@
-# This file is generated by `ray project create`.
-
-name: sanity-check
-
-# description: A short description of the project.
-# The URL of the repo this project is part of.
-# repo: ...
-
-cluster:
-  config: ray-project/cluster.yaml
-
-commands:
-  - name: sanity-check
-    help: "Do release sanity check with pip"
-    command: |      
-      export RAY_VERSION={{ray_version}}
-      export RAY_HASH={{commit}}
-      chmod +x ./pip_download_test.sh
-      ./pip_download_test.sh
-    params:
-    - name: ray_version # Ray version string.
-      default: "1.1.0.dev0"
-
-    - name: commit # Ray commit SHA string.
-      default: "FILL ME IN"
-
-# Pathnames for files and directories that should be saved
-# in a snapshot but that should not be synced with a# session. Pathnames can be relative to the project
-# directory or absolute. Generally, this should be files
-# that were created by an active session, such as
-# application checkpoints and logs.
-output_files: [
-  # For example, uncomment this to save the logs from the
-  # last ray job.
-  # "/tmp/ray/session_latest",
-]
diff --git a/doc/source/profiling.rst b/doc/source/profiling.rst
index 2b7d4638f..ed1d258e7 100644
--- a/doc/source/profiling.rst
+++ b/doc/source/profiling.rst
@@ -74,7 +74,7 @@ To run a set of single-node Ray microbenchmarks, use:
 
   ray microbenchmark
 
-You can find the microbenchmark results for Ray releases in the `GitHub release logs <https://github.com/ray-project/ray/tree/master/doc/dev/release_logs>`__.
+You can find the microbenchmark results for Ray releases in the `GitHub release logs <https://github.com/ray-project/ray/tree/master/release/release_logs>`__.
 
 References
 ----------
diff --git a/release/1.0.0.env b/release/1.0.0.env
deleted file mode 100644
index 26eed1dd5..000000000
--- a/release/1.0.0.env
+++ /dev/null
@@ -1,2 +0,0 @@
-export ray_version="1.0.0rc1"
-export commit=fd5ddb661e659c2b0c968661d96d0405426912e5
diff --git a/release/README.md b/release/README.md
deleted file mode 100644
index 77c79e9e7..000000000
--- a/release/README.md
+++ /dev/null
@@ -1,2 +0,0 @@
-Running the kickoff script:
-
diff --git a/release/RELEASE_PROCESS.rst b/release/RELEASE_PROCESS.rst
deleted file mode 120000
index abd0e53fa..000000000
--- a/release/RELEASE_PROCESS.rst
+++ /dev/null
@@ -1 +0,0 @@
-../doc/dev/RELEASE_PROCESS.rst
\ No newline at end of file
diff --git a/release/RELEASE_PROCESS.rst b/release/RELEASE_PROCESS.rst
new file mode 100644
index 000000000..8ea99d4f4
--- /dev/null
+++ b/release/RELEASE_PROCESS.rst
@@ -0,0 +1,209 @@
+Release Process
+===============
+
+This document describes the process for creating new releases.
+
+1. **Create a release branch:** Create the branch from the desired commit on master
+   In order to create the branch, locally checkout the commit ID i.e.,
+   ``git checkout <hash>``. Then checkout a new branch of the format
+   ``releases/<release-version>``. Then push that branch to the ray repo:
+   ``git push upstream releases/<release-version>``.
+
+2. **Update the release branch version:** Push a commit directly to the
+   newly-created release branch that increments the Python package version in
+   python/ray/__init__.py and src/ray/raylet/main.cc. See this
+   `sample commit for bumping the release branch version`_.
+
+3. **Update the master branch version:**
+
+   For a new minor release (e.g., 0.7.0): Create a pull request to
+   increment the dev version in of the master branch. See this
+   `sample PR for bumping a minor release version`_. **NOTE:** Not all of
+   the version numbers should be replaced. For example, ``0.7.0`` appears in
+   this file but should not be updated.
+
+   For a new micro release (e.g., 0.7.1): No action is required.
+
+4. **Testing:** Before releasing, the following sets of tests should be run.
+   The results of each of these tests for previous releases are checked in
+   under ``release_logs``, and should be compared against to identify
+   any regressions.
+
+   1. Long-running tests
+
+   .. code-block:: bash
+
+       long_running_tests/README.rst
+
+   Follow the instructions to kick off the tests and check the status of the workloads.
+   These tests should run for at least 24 hours without erroring or hanging (ensure that it is printing new iterations and CPU load is
+   stable in the AWS console).
+
+   2. Long-running multi-node tests
+
+   .. code-block:: bash
+
+      long_running_distributed_tests/README.rst
+
+   Follow the instructions to kick off the tests and check the status of the workloads.
+   These suite of tests are similar to the standard long running tests, except these actually run in a multi-node cluster instead of just a simulated one.
+   These tests should also run for at least 24 hours without erroring or hanging.
+
+   **IMPORTANT**: check that the test are actually running (printing output regularly) and aren't
+   just stuck at an iteration. You must also check that the node CPU usage is stable
+   (and not increasing or decreasing over time, which indicates a leak). You can see the head node
+   and worker node CPU utilizations in the AWS console.
+
+   3. Multi-node regression tests
+
+   Follow the same instruction as long running stress tests. The large scale distributed
+   regression tests identify potential performance regression in distributed environment.
+   The following test should be ran:
+
+   - ``rllib_tests/regression_tests`` run the compact regression test for rllib.
+   - ``rllib_tests/stress_tests`` run multinode 8hr IMPALA trial.
+   - ``stress_tests`` contains two tests: ``many_tasks`` and ``dead_actors``.
+     Each of the test runs on 105 spot instances.
+   - ``stress_tests/workloads/placement_group`` contains a Python script to run tests.
+     It currently uses ``cluster_util`` to emulate the cluster testing. It will be converted to 
+     real multi-node tests in the future. For now, just make sure the test succeed locally.
+
+   Make sure that these pass. For the RLlib regression tests, there shouldn't be any errors
+   and the rewards should be similar to previous releases. For the rest, it will be obvious if
+   they passed.  This will use the autoscaler to start a bunch of machines and run some tests.
+
+   **IMPORTANT**: You must get signoff from the RLlib team for the RLlib test results.
+
+   The summaries printed by each test should be checked in under
+   ``release_logs/<version>`` on the **master** branch (make a pull request).
+
+   4. Microbenchmarks
+
+   Run the ``microbenchmark`` with the commit. Under the hood, the session will
+   run `ray microbenchmark` on an `m4.16xl` instance running `Ubuntu 18.04` with `Python 3`
+   to get the latest microbenchmark numbers.
+
+   The results should be checked in under ``release_logs/<version>``.
+
+   You can also get the performance change rate from the previous version using
+   ``util/microbenchmark_analysis.py``.
+
+   5. ASAN tests
+
+   Run the ``ci/asan_tests`` with the commit. This will enable ASAN build and run the
+   whole Python tests to detect memory leaks.
+
+5. **Resolve release-blockers:** If a release blocking issue arises, there are
+   two ways the issue can be resolved: 1) Fix the issue on the master branch and
+   cherry-pick the relevant commit  (using ``git cherry-pick``) onto the release
+   branch (recommended). 2) Revert the commit that introduced the bug on the
+   release branch (using ``git revert``), but not on the master (not recommended).
+
+   These changes should then be pushed directly to the release branch.
+
+6. **Create a GitHub release:** Create a `GitHub release`_. This should include
+   **release notes**. Copy the style and formatting used by previous releases.
+   Create a draft of the release notes containing information about substantial
+   changes/updates/bugfixes and their PR numbers. Once you have a draft, send it
+   out to other Ray developers (especially those who contributed heavily during
+   this release) for feedback. At the end of the release note, you should also
+   add a list of contributors. Make sure Ray, Tune, RLLib, Autoscaler are
+   capitalized correctly.
+
+   Run ``util/get_contributors.py`` to generate the list of commits corresponding
+   to this release and the formatted list of contributors.
+   You will need to provide a GitHub personal access token
+   (github.com -> settings -> developer settings -> personal access tokens).
+
+    .. code-block:: bash
+
+      # Must be run from inside the Ray repository.
+      pip install PyGitHub tqdm
+      python get_contributors.py --help
+      python get_contributors.py \
+        --access-token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
+        --prev-release-commit="<COMMIT_SHA>" \
+        --curr-release-commit="<COMMIT_SHA>"
+
+7. **Download all the wheels:** Now the release is ready to begin final
+   testing. The wheels are automatically uploaded to S3, even on the release
+   branch. To download them, use ``util/download_wheels.sh``:
+
+   .. code-block:: bash
+
+       export RAY_HASH=...  # e.g., 618147f57fb40368448da3b2fb4fd213828fa12b
+       export RAY_VERSION=...  # e.g., 0.7.0
+       ./bin/download_wheels.sh
+
+   This can be tested if you use the script source ./bin/download_wheels.sh
+
+8. **Upload to PyPI Test:** Upload the wheels to the PyPI test site using
+   ``twine``.
+
+   .. code-block:: bash
+
+     # Downloads all of the wheels to the current directory.
+     RAY_VERSION=<version> RAY_HASH=<commit_sha> bash download_wheels.sh
+
+     # Will ask for your PyPI test credentials and require that you're a maintainer
+     # on PyPI test. If you are not, ask @robertnishihara to add you.
+     pip install twine
+     twine upload --repository-url https://test.pypi.org/legacy/ *.whl
+
+   Test that you can install the wheels with pip from the PyPI test repository:
+
+   .. code-block:: bash
+
+     # First install ray normally because installing from test.pypi.org won't
+     # be able to install some of the other dependencies.
+     pip install ray
+     pip uninstall ray
+
+     pip install --index-url https://test.pypi.org/simple/ ray
+
+   Then start Python, make sure you can ``import ray`` and run some simple Ray
+   scripts. Make sure that it is finding the version of Ray that you just
+   installed by checking ``ray.__version__`` and ``ray.__file__``.
+
+   Do this for MacOS, Linux, and Windows.
+
+   This process is automated. Run ./bin/pip_download_test.sh.
+   This will download the ray from the test pypi repository and run the minimum
+   sanity check from all the Python version supported. (3.6, 3.7, 3.8)
+
+   Windows sanity check test is currently not automated.
+
+9. **Upload to PyPI:** Now that you've tested the wheels on the PyPI test
+   repository, they can be uploaded to the main PyPI repository. Be careful,
+   **it will not be possible to modify wheels once you upload them**, so any
+   mistake will require a new release.
+
+   .. code-block:: bash
+
+     # Will ask for your real PyPI credentials and require that you're a maintainer
+     # on real PyPI. If you are not, ask @robertnishihara to add you.
+     twine upload --repository-url https://upload.pypi.org/legacy/ *.whl
+
+   Now, try installing from the real PyPI mirror. Verify that the correct version is
+   installed and that you can run some simple scripts.
+
+   .. code-block:: bash
+
+     pip install -U ray
+
+10. **Create a point release on readthedocs page:** Go to the `Ray Readthedocs version page`_.
+    Scroll to "Activate a version" and mark the *release branch* as "active" and "public". This creates a point release for the documentation.
+    Message @richardliaw to add you if you don't have access.
+
+11. **Update 'Default Branch' on the readthedocs page:** Go to the `Ray Readthedocs advanced settings page`_.
+    In 'Global Settings', set the 'Default Branch' to the *release branch*. This redirects the documentation to the latest pip release.
+    Message @richardliaw to add you if you don't have access.
+
+12. **Improve the release process:** Find some way to improve the release
+    process so that whoever manages the release next will have an easier time.
+
+.. _`sample PR for bumping a minor release version`: https://github.com/ray-project/ray/pull/6303
+.. _`sample commit for bumping the release branch version`: https://github.com/ray-project/ray/commit/a39325d818339970e51677708d5596f4b8f790ce
+.. _`GitHub release`: https://github.com/ray-project/ray/releases
+.. _`Ray Readthedocs version page`: https://readthedocs.org/projects/ray/versions/
+.. _`Ray Readthedocs advanced settings page`: https://readthedocs.org/dashboard/ray/advanced/
diff --git a/doc/dev/release_logs/0.7.7/microbenchmark.txt b/release/release_logs/0.7.7/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.7.7/microbenchmark.txt
rename to release/release_logs/0.7.7/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.7.7/rllib_regression.txt b/release/release_logs/0.7.7/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.7.7/rllib_regression.txt
rename to release/release_logs/0.7.7/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.7.7/stress_tests/test_dead_actors.txt b/release/release_logs/0.7.7/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.7.7/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.7.7/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.7.7/stress_tests/test_many_tasks.txt b/release/release_logs/0.7.7/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.7.7/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.7.7/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.0/microbenchmark.txt b/release/release_logs/0.8.0/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.0/microbenchmark.txt
rename to release/release_logs/0.8.0/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.0/rllib_regression.txt b/release/release_logs/0.8.0/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.0/rllib_regression.txt
rename to release/release_logs/0.8.0/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.0/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.0/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.0/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.0/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.0/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.0/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.0/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.0/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.1/microbenchmark.txt b/release/release_logs/0.8.1/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.1/microbenchmark.txt
rename to release/release_logs/0.8.1/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.1/rllib_regression.txt b/release/release_logs/0.8.1/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.1/rllib_regression.txt
rename to release/release_logs/0.8.1/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.1/stress_tests/application_stress_test.txt b/release/release_logs/0.8.1/stress_tests/application_stress_test.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.1/stress_tests/application_stress_test.txt
rename to release/release_logs/0.8.1/stress_tests/application_stress_test.txt
diff --git a/doc/dev/release_logs/0.8.1/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.1/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.1/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.1/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.1/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.1/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.1/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.1/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.2/microbenchmark.txt b/release/release_logs/0.8.2/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.2/microbenchmark.txt
rename to release/release_logs/0.8.2/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.2/rllib_regression.txt b/release/release_logs/0.8.2/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.2/rllib_regression.txt
rename to release/release_logs/0.8.2/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.2/stress_tests/application_stress_test.txt b/release/release_logs/0.8.2/stress_tests/application_stress_test.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.2/stress_tests/application_stress_test.txt
rename to release/release_logs/0.8.2/stress_tests/application_stress_test.txt
diff --git a/doc/dev/release_logs/0.8.2/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.2/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.2/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.2/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.2/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.2/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.2/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.2/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.3/microbenchmark.txt b/release/release_logs/0.8.3/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.3/microbenchmark.txt
rename to release/release_logs/0.8.3/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.3/rllib_regression.txt b/release/release_logs/0.8.3/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.3/rllib_regression.txt
rename to release/release_logs/0.8.3/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.3/stress_tests/application_stress_test.txt b/release/release_logs/0.8.3/stress_tests/application_stress_test.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.3/stress_tests/application_stress_test.txt
rename to release/release_logs/0.8.3/stress_tests/application_stress_test.txt
diff --git a/doc/dev/release_logs/0.8.3/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.3/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.3/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.3/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.3/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.3/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.3/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.3/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.4/microbenchmark.txt b/release/release_logs/0.8.4/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.4/microbenchmark.txt
rename to release/release_logs/0.8.4/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.4/rllib_regression.txt b/release/release_logs/0.8.4/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.4/rllib_regression.txt
rename to release/release_logs/0.8.4/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.4/stress_tests/application_stress_test.txt b/release/release_logs/0.8.4/stress_tests/application_stress_test.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.4/stress_tests/application_stress_test.txt
rename to release/release_logs/0.8.4/stress_tests/application_stress_test.txt
diff --git a/doc/dev/release_logs/0.8.4/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.4/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.4/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.4/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.4/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.4/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.4/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.4/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.5/microbenchmark.txt b/release/release_logs/0.8.5/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.5/microbenchmark.txt
rename to release/release_logs/0.8.5/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.5/rllib_regression.txt b/release/release_logs/0.8.5/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.5/rllib_regression.txt
rename to release/release_logs/0.8.5/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.5/stress_tests/application_stress_test.txt b/release/release_logs/0.8.5/stress_tests/application_stress_test.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.5/stress_tests/application_stress_test.txt
rename to release/release_logs/0.8.5/stress_tests/application_stress_test.txt
diff --git a/doc/dev/release_logs/0.8.5/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.5/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.5/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.5/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.5/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.5/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.5/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.5/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.6/microbenchmark.txt b/release/release_logs/0.8.6/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.6/microbenchmark.txt
rename to release/release_logs/0.8.6/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.6/rllib_regression.txt b/release/release_logs/0.8.6/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.6/rllib_regression.txt
rename to release/release_logs/0.8.6/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.6/stress_tests/application_stress_test.txt b/release/release_logs/0.8.6/stress_tests/application_stress_test.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.6/stress_tests/application_stress_test.txt
rename to release/release_logs/0.8.6/stress_tests/application_stress_test.txt
diff --git a/doc/dev/release_logs/0.8.6/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.6/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.6/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.6/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.6/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.6/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.6/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.6/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/0.8.7/microbenchmark.txt b/release/release_logs/0.8.7/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.7/microbenchmark.txt
rename to release/release_logs/0.8.7/microbenchmark.txt
diff --git a/doc/dev/release_logs/0.8.7/rllib_regression.txt b/release/release_logs/0.8.7/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.7/rllib_regression.txt
rename to release/release_logs/0.8.7/rllib_regression.txt
diff --git a/doc/dev/release_logs/0.8.7/stress_tests/application_stress_test.txt b/release/release_logs/0.8.7/stress_tests/application_stress_test.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.7/stress_tests/application_stress_test.txt
rename to release/release_logs/0.8.7/stress_tests/application_stress_test.txt
diff --git a/doc/dev/release_logs/0.8.7/stress_tests/test_dead_actors.txt b/release/release_logs/0.8.7/stress_tests/test_dead_actors.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.7/stress_tests/test_dead_actors.txt
rename to release/release_logs/0.8.7/stress_tests/test_dead_actors.txt
diff --git a/doc/dev/release_logs/0.8.7/stress_tests/test_many_tasks.txt b/release/release_logs/0.8.7/stress_tests/test_many_tasks.txt
similarity index 100%
rename from doc/dev/release_logs/0.8.7/stress_tests/test_many_tasks.txt
rename to release/release_logs/0.8.7/stress_tests/test_many_tasks.txt
diff --git a/doc/dev/release_logs/1.0.0/microbenchmark.txt b/release/release_logs/1.0.0/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/1.0.0/microbenchmark.txt
rename to release/release_logs/1.0.0/microbenchmark.txt
diff --git a/doc/dev/release_logs/1.0.1/microbenchmark.txt b/release/release_logs/1.0.1/microbenchmark.txt
similarity index 100%
rename from doc/dev/release_logs/1.0.1/microbenchmark.txt
rename to release/release_logs/1.0.1/microbenchmark.txt
diff --git a/doc/dev/release_logs/1.0.1/rllib_regression.txt b/release/release_logs/1.0.1/rllib_regression.txt
similarity index 100%
rename from doc/dev/release_logs/1.0.1/rllib_regression.txt
rename to release/release_logs/1.0.1/rllib_regression.txt
diff --git a/release/rllib_tests/regression_tests/compact-regression-test.yaml b/release/rllib_tests/regression_tests/compact-regression-test.yaml
index 90349a069..7c5d633b8 100644
--- a/release/rllib_tests/regression_tests/compact-regression-test.yaml
+++ b/release/rllib_tests/regression_tests/compact-regression-test.yaml
@@ -4,7 +4,7 @@
 # rewards reached seem reasonably in line with previous results.
 #
 # You can find the reference results here:
-# https://github.com/ray-project/ray/tree/master/doc/dev/release_logs
+# https://github.com/ray-project/ray/tree/master/release/release_logs
 atari-impala:
     env: BreakoutNoFrameskip-v4
     run: IMPALA
diff --git a/doc/dev/download_wheels.sh b/release/util/download_wheels.sh
similarity index 85%
rename from doc/dev/download_wheels.sh
rename to release/util/download_wheels.sh
index 163e87921..bcb58b81e 100644
--- a/doc/dev/download_wheels.sh
+++ b/release/util/download_wheels.sh
@@ -10,16 +10,17 @@ if [[ -z "$RAY_VERSION" ]]; then
     exit 1
 fi
 
-# Make sure Linux wheels are downloadable without errors.
+# Linux.
 wget "https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp36-cp36m-manylinux2014_x86_64.whl"
 wget "https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp37-cp37m-manylinux2014_x86_64.whl"
 wget "https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp38-cp38-manylinux2014_x86_64.whl"
-# Make sure macos wheels are downloadable without errors.
+
+# macOS.
 wget "https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp36-cp36m-macosx_10_13_intel.whl"
 wget "https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp37-cp37m-macosx_10_13_intel.whl"
-# Wheel name convention has been changed from Python 3.8.
 wget "https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp38-cp38-macosx_10_13_x86_64.whl"
-# Make sure Windows wheels are downloadable without errors.
+
+# Windows.
 wget "https://ray-wheels.s3-us-west-2.amazonaws.com/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp36-cp36m-win_amd64.whl"
 wget "https://ray-wheels.s3-us-west-2.amazonaws.com/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp37-cp37m-win_amd64.whl"
 wget "https://ray-wheels.s3-us-west-2.amazonaws.com/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp38-cp38-win_amd64.whl"
diff --git a/doc/dev/get_contributors.py b/release/util/get_contributors.py
similarity index 100%
rename from doc/dev/get_contributors.py
rename to release/util/get_contributors.py
diff --git a/release/kickoff.sh b/release/util/kickoff.sh
similarity index 100%
rename from release/kickoff.sh
rename to release/util/kickoff.sh
diff --git a/doc/dev/microbenchmark_analysis.py b/release/util/microbenchmark_analysis.py
similarity index 100%
rename from doc/dev/microbenchmark_analysis.py
rename to release/util/microbenchmark_analysis.py
diff --git a/doc/dev/bin/pip_download_test.sh b/release/util/pip_download_test.sh
similarity index 100%
rename from doc/dev/bin/pip_download_test.sh
rename to release/util/pip_download_test.sh
diff --git a/doc/dev/bin/sanity_check.py b/release/util/sanity_check.py
similarity index 100%
rename from doc/dev/bin/sanity_check.py
rename to release/util/sanity_check.py
diff --git a/rllib/tuned_examples/compact-regression-test.yaml b/rllib/tuned_examples/compact-regression-test.yaml
index 90349a069..7c5d633b8 100644
--- a/rllib/tuned_examples/compact-regression-test.yaml
+++ b/rllib/tuned_examples/compact-regression-test.yaml
@@ -4,7 +4,7 @@
 # rewards reached seem reasonably in line with previous results.
 #
 # You can find the reference results here:
-# https://github.com/ray-project/ray/tree/master/doc/dev/release_logs
+# https://github.com/ray-project/ray/tree/master/release/release_logs
 atari-impala:
     env: BreakoutNoFrameskip-v4
     run: IMPALA