docs: split out release steps into separate doc (#2615) Move the steps for releasing into a separate doc. The release steps are specific to releases, which only maintainers do. This frees up space in the developing docs for more general tips, tricks, and guidance for others. Along the way... * Remove the text about the core rules being part of Bazel * Put the CLA text first -- if CLAs aren't signed _before_ code is given, it can result is large headaches. * Move some more internal dev steps out of contributing docs.
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.