Bump dev branch to 2.0 to avoid endless version bump toil (#13497)

* wip

* fix

* fix

release/RELEASE_PROCESS.rst

@@ -40,32 +40,7 @@ After Branch Cut
    ``python/ray/__init__.py``, ``src/ray/raylet/main.cc``, and any other files that use ``ray::stats::VersionKey``. See this
    `sample commit for bumping the release branch version`_.
 
-3. **Create PR to update the master branch version:**
-   For a new minor release (e.g., ``0.6.3 -> 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.
-   You will want to replace all instances of nightly wheel links (wheels with
-   dev in their name), instances of ``ray::stats::VersionKey``,
-   and instances of ``__version__``.
-
-   TIP: search the code base for instances of ``https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-1.1.0.dev0`` (but replace ray-1.1.0 with the current version) to find links to the nightly wheel to update.
-
-   You should also cherry pick parts of this pull request referencing the
-   latest wheels onto the release branch prior
-   to making the release. This will ensure that the ``install-nightly`` of
-   the new release correctly points at the latest version on master.
-
-   Note: Doing this will cause the ``install-nightly`` CLI command of the
-   current Ray release to fail, so you should only merge this PR when
-   the release is about to occur. (For instance, the 1.0.0 ``install-nightly``
-   command points to 1.1.0.dev0, so when you bump master to 1.2.0.dev0, it no
-   longer finds the latest commit.)
-
-   For a new micro release (e.g., ``0.7.0 -> 0.7.1``): No action is required.
-
-4. **Create a document to collect release-notes:** You can clone `this document <https://docs.google.com/document/d/1vzcNHulHCrq1PrXWkGBwwtOK53vY2-Ol8SXbnvKPw1s/edit?usp=sharing>`_.
+3. **Create a document to collect release-notes:** You can clone `this document <https://docs.google.com/document/d/1vzcNHulHCrq1PrXWkGBwwtOK53vY2-Ol8SXbnvKPw1s/edit?usp=sharing>`_.
 
    You will also need to create a spreadsheet with information about the PRs 
    included in the release to jog people's memories. You can collect this

release/long_running_distributed_tests/cluster.yaml

@@ -30,7 +30,7 @@ worker_nodes:
 
 setup_commands:
   - apt-get install -y libglib2.0-0 libcudnn7=7.6.5.32-1+cuda10.1
-  - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-1.2.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
+  - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
 
 # Command to start ray on the head node. You don't need to change this.
 head_start_ray_commands:

release/rllib_tests/regression_tests/cluster.yaml

@@ -25,7 +25,7 @@ head_node:
 # List of shell commands to run to set up nodes.
 setup_commands:
     - apt-get install -y libglib2.0-0 libcudnn7=7.6.5.32-1+cuda10.1
-    - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-1.2.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
+    - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
 
 # Command to start ray on the head node. You don't need to change this.
 head_start_ray_commands:

release/rllib_tests/stress_tests/cluster.yaml

@@ -33,7 +33,7 @@ file_mounts: {
 
 setup_commands:
     - apt-get install -y libglib2.0-0 libcudnn7=7.6.5.32-1+cuda10.1
-    - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-1.2.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
+    - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
 
 worker_setup_commands: []
 

release/stress_tests/autoscaler-cluster.yaml

@@ -98,7 +98,7 @@ setup_commands:
     - pip install terminado
     - pip install boto3==1.4.8 cython==0.29.0
     # - cd ray/python; git checkout master; git pull; pip install -e . --verbose
-    - pip install -U pip install https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-1.2.0.dev0-cp38-cp38-manylinux2014_x86_64.whl
+    - pip install -U pip install https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp38-cp38-manylinux2014_x86_64.whl
 
 # Custom commands that will be run on the head node after common setup.
 head_setup_commands: []

release/stress_tests/cluster.yaml

@@ -89,7 +89,7 @@ setup_commands:
     - pip install terminado
     - pip install boto3==1.4.8 cython==0.29.0
     # - cd ray/python; git checkout master; git pull; pip install -e . --verbose
-    - "pip install https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-1.2.0.dev0-cp38-cp38-manylinux2014_x86_64.whl"
+    - "pip install https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp38-cp38-manylinux2014_x86_64.whl"
 # Custom commands that will be run on the head node after common setup.
 head_setup_commands: []
 

release/tune_tests/scalability_tests/cluster.yaml

@@ -30,4 +30,4 @@ worker_nodes:
     InstanceType: m5.16xlarge
 
 setup_commands:
-    - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-1.2.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
+    - pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl