Skip to content

doc: keep the README release table in sync with the releases#294

Merged
daniel-rossier merged 1 commit into
mainfrom
docs/release-table-update
Jul 15, 2026
Merged

doc: keep the README release table in sync with the releases#294
daniel-rossier merged 1 commit into
mainfrom
docs/release-table-update

Conversation

@daniel-rossier

Copy link
Copy Markdown
Contributor

The Maintained versions table in the README still advertised v6.2.1 as the latest 6.2 release while v6.2.2 and v6.2.3 have been published — nothing in the release process mentioned the table, so it drifted silently.

  • Point the 6.2 line at v6.2.3 (the current Latest).
  • 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 (so3_X.Y.Z.bb/avz_X.Y.Z.bb recipes + PREFERRED_VERSION in local.conf), as was done manually for the v6.2.2/v6.2.3 releases.

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.
@daniel-rossier
daniel-rossier merged commit 05772bf into main Jul 15, 2026
6 checks passed
@daniel-rossier
daniel-rossier deleted the docs/release-table-update branch July 15, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant