mirror of
https://github.com/wassname/ray.git
synced 2026-08-12 12:20:11 +08:00
Improve release process from 0.8.2 (#7303)
This commit is contained in:
Simon Mo
+31
-25
@@ -24,9 +24,10 @@ This document describes the process for creating new releases.
|
||||
|
||||
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_tests``,
|
||||
and should be compared against to identify any regressions.
|
||||
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_tests``, and should be compared against to identify
|
||||
any regressions.
|
||||
|
||||
1. Long-running tests
|
||||
|
||||
@@ -38,16 +39,16 @@ This document describes the process for creating new releases.
|
||||
These tests should run for at least 24 hours (printing new iterations and CPU load
|
||||
stable in the AWS console).
|
||||
|
||||
The last hundred lines or so printed by each test should be checked in under
|
||||
``doc/dev/release_logs/<version>``.
|
||||
2. Multi-node regression tests
|
||||
|
||||
2. Stress 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:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
ray/ci/stress_tests/run_stress_tests.sh <release-version> <release-commit>
|
||||
ray/ci/stress_tests/run_application_stress_tests.sh <release-version> <release-commit>
|
||||
rllib train -f rllib/tuned_examples/compact-regression-test.yaml
|
||||
- ``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.
|
||||
|
||||
Make sure that these pass. For the RLlib regression tests, see the comment on the
|
||||
file for the pass criteria. For the rest, it will be obvious if they passed.
|
||||
@@ -59,12 +60,9 @@ This document describes the process for creating new releases.
|
||||
|
||||
3. Microbenchmarks
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
ray microbenchmark
|
||||
|
||||
Run `ray microbenchmark` on an `m4.16xl` instance running `Ubuntu 18.04` with `Python 3` to get the
|
||||
latest microbenchmark numbers.
|
||||
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>``.
|
||||
|
||||
@@ -82,10 +80,11 @@ This document describes the process for creating new releases.
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
|
||||
@@ -107,14 +106,16 @@ This document describes the process for creating new releases.
|
||||
|
||||
export RAY_HASH=... # e.g., 618147f57fb40368448da3b2fb4fd213828fa12b
|
||||
export RAY_VERSION=... # e.g., 0.7.0
|
||||
pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp27-cp27mu-manylinux1_x86_64.whl
|
||||
|
||||
# Linux Wheels
|
||||
pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp35-cp35m-manylinux1_x86_64.whl
|
||||
pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp36-cp36m-manylinux1_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-manylinux1_x86_64.whl
|
||||
pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp27-cp27m-macosx_10_6_intel.whl
|
||||
pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp35-cp35m-macosx_10_6_intel.whl
|
||||
pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp36-cp36m-macosx_10_6_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_6_intel.whl
|
||||
|
||||
# Mac Wheels
|
||||
pip install -U https://s3-us-west-2.amazonaws.com/ray-wheels/releases/$RAY_VERSION/$RAY_HASH/ray-$RAY_VERSION-cp35-cp35m-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-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
|
||||
|
||||
8. **Upload to PyPI Test:** Upload the wheels to the PyPI test site using
|
||||
``twine``.
|
||||
@@ -164,9 +165,14 @@ This document describes the process for creating new releases.
|
||||
|
||||
pip install -U ray
|
||||
|
||||
10. **Improve the release process:** Find some way to improve the release
|
||||
10. **Create a point release on readthedocs page:** In the `read the docs project page`_,
|
||||
mark the release branch as "active" so there is a point release for the documentation.
|
||||
Add @richardliaw to add you if you don't have access.
|
||||
|
||||
11. **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
|
||||
.. _`read the docs project page`: https://readthedocs.org/projects/ray/
|
||||
|
||||
Reference in New Issue
Block a user