From 644c5f661776c9ddabea8ac3976ed4348c0f5812 Mon Sep 17 00:00:00 2001 From: Greg Date: Sun, 23 Jun 2024 09:30:21 +1000 Subject: [PATCH 1/2] Update README --- README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/README.md b/README.md index 546af97009..179655fd82 100644 --- a/README.md +++ b/README.md @@ -13,13 +13,9 @@ Documentation for rules_python is at and i Examples live in the [examples](examples) directory. -Currently, the core rules build into the Bazel binary, and the symbols in this -repository are simple aliases. However, we are migrating the rules to Starlark and removing them from the Bazel binary. Therefore, the future-proof way to depend on Python rules is via this repository. See[`Migrating from the Bundled Rules`](#Migrating-from-the-bundled-rules) below. - The core rules are stable. Their implementation in Bazel is subject to Bazel's [backward compatibility policy](https://docs.bazel.build/versions/master/backward-compatibility.html). -Once migrated to rules_python, they may evolve at a different -rate, but this repository will still follow [semantic versioning](https://semver.org). +This repository aims to follow [semantic versioning](https://semver.org). 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](CONTRIBUTING.md) page for information on our development workflow. From 1055f12384e492551576796931a817454ed9b660 Mon Sep 17 00:00:00 2001 From: Greg Roodt Date: Sun, 23 Jun 2024 11:29:29 +1000 Subject: [PATCH 2/2] Update README.md Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 179655fd82..d890d702d6 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ Documentation for rules_python is at and i Examples live in the [examples](examples) directory. -The core rules are stable. Their implementation in Bazel is subject to Bazel's +The core rules are stable. Their implementation is subject to Bazel's [backward compatibility policy](https://docs.bazel.build/versions/master/backward-compatibility.html). This repository aims to follow [semantic versioning](https://semver.org).