On Wed Sep 2, 2026 at 11:59 AM CEST, Daniel Turull via lists.openembedded.org wrote: > From: Daniel Turull <[email protected]> > > lttng-tools maintains a branch per minor series (stable-2.11 through > stable-2.16) and tags point releases from it, releasing from more than one > at a time: 2.14.2 and 2.15.1 went out the same day. So upgrades within a > major.minor are stable point upgrades per the OE-Core stable release > policy (ref-manual, "Stable Point Release Upgrades"). There is no written > policy document, so qualification rests on the branch structure and the > release contents below.
I found this: https://github.com/lttng/lttng-tools/tree/stable-2.15#supported-versions: |== Supported versions | |The LTTng project supports the last two released stable versions |(e.g. stable-2.13 and stable-2.12). | |Fixes are backported from the master branch to the last stable version unless |those fixes would break the ABI or API. Those fixes may be backported to the |second-last stable version, depending on complexity and ABI/API compatibility. | |Security fixes are backported from the master branch to both of the last stable |version and the second-last stable version. | |New features are integrated into the master branch and not backported to the |last stable branch. I've added that to the commit in my branch. I've noticed that it's very easy for a LLM to hallucinate a negative answer: "This does not exist". > > https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades > https://github.com/lttng/lttng-tools/blob/v2.15.1/ChangeLog > https://github.com/lttng/lttng-tools/tree/stable-2.15 > > Upstream keeps a ChangeLog with a per-release entry list, and all 48 > entries for 2.15.1 (Jun 05 2026, against 2.15.0 in February) are fixes, > tests, documentation or refactors. Seven address machine interface output > alone; the rest cover a consumerd lockfile fd leak across fork+exec, a > missing default kernel probe entry, an uninitialised read in uri_compare, > a musl compatibility fix, popt error handling, test fixes, and one > refactor preparing the CPU-mask escaping fix. > > Already tracked this way on the OE stable branches, counting only bumps > since each branch forked: kirkstone took 2.13.4 -> 2.13.8 and 2.13.8 -> > 2.13.9, scarthgap 2.13.11 -> 2.13.13. wrynose has taken none and sits at > 2.14.1. > > AI-Generated: Kiro with Claude Opus 5 > Signed-off-by: Daniel Turull <[email protected]> > Signed-off-by: Mathieu Dubois-Briand <[email protected]> > > Adapted for wrynose: applied to lttng-tools_2.14.1.bb (upstream: > lttng-tools_2.15.1.bb). > (cherry picked from commit 40f22582ff6989f9275808bfda229a8ec78504e4) > --- > meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb > b/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb > index 3a3f2cff2c..3df9ed1c00 100644 > --- a/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb > +++ b/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb > @@ -54,7 +54,7 @@ SRC_URI = > "https://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \ > > SRC_URI[sha256sum] = > "0e68eb27923621c4bc127cfce40422d28cf7e473fedf6229ae6c32ba5c5b7c6d" > > -inherit autotools ptest pkgconfig useradd python3-dir manpages systemd > +inherit autotools ptest pkgconfig useradd python3-dir manpages systemd > upstream-stable-release-point > > CACHED_CONFIGUREVARS = "PGREP=/usr/bin/pgrep" > -- Yoann Congal Smile ECS
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#245987): https://lists.openembedded.org/g/openembedded-core/message/245987 Mute This Topic: https://lists.openembedded.org/mt/121048533/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
