From 5d440cb63c0b47fe4c796dac5e1ed35de4654e6a Mon Sep 17 00:00:00 2001 From: Richard Levasseur Date: Thu, 13 Feb 2025 21:22:44 -0800 Subject: [PATCH] docs: update dev docs on how to pick next version --- DEVELOPING.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/DEVELOPING.md b/DEVELOPING.md index d816fba57f..7f9b6fc1b1 100644 --- a/DEVELOPING.md +++ b/DEVELOPING.md @@ -36,12 +36,13 @@ also test-drive the commit in an existing Bazel workspace to sanity check functi #### Determining Semantic Version -**rules_python** is currently using [Zero-based versioning](https://0ver.org/) and thus backwards-incompatible API -changes still come under the minor-version digit. So releases with API changes and new features bump the minor, and -those with only bug fixes and other minor changes bump the patch digit. +**rules_python** uses [semantic version](https://semver.org), so releases with +API changes and new features bump the minor, and those with only bug fixes and +other minor changes bump the patch digit. To find if there were any features added or incompatible changes made, review -the commit history. This can be done using github by going to the url: +[CHANGELOG.md](CHANGELOG.md) and the commit history. This can be done using +github by going to the url: `https://github.com/bazelbuild/rules_python/compare/...main`. ### Patch release with cherry picks