From a37d7dac0b57b57efe9c46957fa839c1510294c5 Mon Sep 17 00:00:00 2001 From: Daniel Rossier Date: Mon, 10 Aug 2026 21:22:49 +0200 Subject: [PATCH] doc: v6.3.0 release bump Propagate the v6.3.0 release to main, as release_process.rst requires right after a tag (these drift silently otherwise): - the Maintained versions table in README.md (6.3 becomes the current stable line, 6.2 the previous one, 6.1 end of life) - a CHANGELOG entry mirroring the GitHub Release notes - the build-system pins: so3_/avz_ recipes renamed, their PV, and the PREFERRED_VERSION_so3 / PREFERRED_VERSION_avz entries in local.conf SO3_KERNEL_VERSION_FALLBACK is already at 6.3.0: it was bumped before the tag, which is the half that had been missed for v6.2.5. --- CHANGELOG | 32 +++++++++++++++++++ README.md | 5 +-- build/conf/local.conf | 14 ++++---- .../avz/{avz_6.2.5.bb => avz_6.3.0.bb} | 2 +- .../so3/{so3_6.2.5.bb => so3_6.3.0.bb} | 2 +- 5 files changed, 44 insertions(+), 11 deletions(-) rename build/meta-so3/recipes-so3/avz/{avz_6.2.5.bb => avz_6.3.0.bb} (99%) rename build/meta-so3/recipes-so3/so3/{so3_6.2.5.bb => so3_6.3.0.bb} (99%) diff --git a/CHANGELOG b/CHANGELOG index d1671225c..033894f02 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,4 +1,36 @@ +v6.3.0 (12 aug 2026) + +Minor release opening the 6.3 line. It carries the developer build container +and a documentation correctness pass on top of v6.2.5. + + • A ready-made build environment: docker/build-env plus scripts/dbuild.sh. + The image carries only the environment — both Arm 64-bit toolchains, + including the bare-metal aarch64-none-elf the SO3 and AVZ kernels need + and that hand-provisioned hosts routinely miss, the 32-bit apt + toolchains, and the host packages listed in packages.txt. The repository + stays on the host, bind-mounted at its own absolute path so bitbake + stamps and the buildroot host tree stay valid and a tree can be built + from inside or outside the container interchangeably, and the container + runs as the calling host user so nothing comes back root-owned. + One entry point covers everything: dbuild.sh --build to make the image, + a bare dbuild.sh for an interactive shell with env.sh already sourced, + and dbuild.sh