[dist] Release notes for Java And other Languages

Describe your feature request

Ray java release is not well done currently. We need a formal release process for ray java.

Other language that ray will support in future all need a formal release process.

Maven

For every release of ray, we should upload ray jars to maven repository.

Currently ray jars only contains current platform native c++ shared libraries. For maven distribution, we need package native c++ shared libraries of every platform into ray jars, so that users can use same maven dependencies in every platform.

Wheel

For the users of Ray cross-lang, we always need the ray-jars setup. When the Python user wants to create Java actor, ray-jars is needed. Package jars into wheel is a way for this, deploy jars in advance is also viable, but maybe too complicated for users. ray-all package depends on ray package, pip install ray-all will pip install ray automatically if ray is not installed.

So I suggest to release a ray-all wheel dist which contains ray java jars to pypi for every release of ray. Resources of other languages should be packaged into this wheel in future.

If this is viable, #6600 is a simple wheel implementation. We need to determine the name of wheel. Will it be suitable to call it ray-all or ray-java?

If there is a better way, please let me know.

[chaokunyang]

Since we added an extra ray-java wheel, its release should be sync with ray wheel. When we upload ray wheel to pypi, we also need to upload ray-java wheel to pypi.

For maven release, we need release every commit in master as a snapshoot in maven. For every release version of ray wheel in pypi, we should release jars to maven release too.

[chaokunyang]

@robertnishihara ray-java wheel is a separate wheel, packaged by a separate setup.py. It won’t affect ray wheel size. We thought package jars into ray wheel. But it’s too large and not useful for pure python users. So we package jars into a separate wheel. Please take a look at #6600. It’s how we do it.