From ae6f2d878f6d27b65a4a5c358758d02012375dc9 Mon Sep 17 00:00:00 2001 From: Daniel Rossier Date: Wed, 15 Jul 2026 20:59:08 +0200 Subject: [PATCH] doc: keep the README release table in sync with the releases MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Maintained-versions table still advertised v6.2.1 as the latest 6.2 release while v6.2.2 and v6.2.3 had been published — nothing in the release process mentioned it, so it drifted silently. Point the 6.2 line at v6.2.3 and add an 'After tagging' section to the release process covering the two main-branch references every release must bump: the README table and the build-system version pins (recipes + PREFERRED_VERSION), as done for the v6.2.2/v6.2.3 releases. --- README.md | 2 +- doc/source/release_process.rst | 15 +++++++++++++++ 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index e47827168..311788037 100644 --- a/README.md +++ b/README.md @@ -79,7 +79,7 @@ land there and are tagged as patch releases. | Line | Branch | Latest release | Status | |------|--------|----------------|--------| -| 6.2 | [`release/v6.2`](https://github.com/smartobjectoriented/so3/tree/release/v6.2) | [v6.2.1](https://github.com/smartobjectoriented/so3/releases/tag/v6.2.1) | Current stable | +| 6.2 | [`release/v6.2`](https://github.com/smartobjectoriented/so3/tree/release/v6.2) | [v6.2.3](https://github.com/smartobjectoriented/so3/releases/tag/v6.2.3) | Current stable | | 6.1 | [`release/v6.1`](https://github.com/smartobjectoriented/so3/tree/release/v6.1) | [v6.1.0](https://github.com/smartobjectoriented/so3/releases/tag/v6.1.0) | Previous | | 5.4 | [`release/v5.4`](https://github.com/smartobjectoriented/so3/tree/release/v5.4) | [v5.4.1](https://github.com/smartobjectoriented/so3/releases/tag/v5.4.1) | End of life | diff --git a/doc/source/release_process.rst b/doc/source/release_process.rst index c49a59214..ca07ad3b5 100644 --- a/doc/source/release_process.rst +++ b/doc/source/release_process.rst @@ -124,6 +124,21 @@ When ``main`` is ready for a new minor version, branch off it, then tag: gh release create v6.3.0 --title "SO3 v6.3.0" \ --target release/v6.3 --latest --generate-notes +After tagging: propagate the release to ``main`` +************************************************ + +A release is not finished when the tag is pushed. Two references to the +current version live on ``main`` and must be bumped right after every +release (they drift silently otherwise): + +* the *Maintained versions* table in ``README.md`` (the *Latest release* + column of the line, and the *Status* column when a new minor line starts); +* the build-system version pins: rename the ``so3_X.Y.Z.bb`` and + ``avz_X.Y.Z.bb`` recipes (under ``build/meta-so3/recipes-so3/``) to the + new version and update the ``PREFERRED_VERSION_so3`` / + ``PREFERRED_VERSION_avz`` entries in ``build/conf/local.conf`` (see the + ``v6.2.3`` bump for a template). + Rules of thumb **************