Update release information from 0.8.6. (#9124)

* [BRING BACK TO MASTER] Update release information.

* [MERGE TO MASTER] Add microbenchmark result.

* Update asan tests to the doc.

doc/dev/RELEASE_PROCESS.rst

@@ -49,7 +49,7 @@ This document describes the process for creating new releases.
    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.
 
-   2. Multi-node regression tests
+   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.
@@ -68,7 +68,7 @@ This document describes the process for creating new releases.
    The summaries printed by each test should be checked in under
    ``doc/dev/release_logs/<version>``.
 
-   3. Microbenchmarks
+   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`
@@ -79,6 +79,11 @@ This document describes the process for creating new releases.
    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
@@ -160,12 +165,13 @@ This document describes the process for creating new releases.
    scripts. Make sure that it is finding the version of Ray that you just
    installed by checking ``ray.__version__`` and ``ray.__file__``.
 
-   Do this at least for MacOS and Linux.
+   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,