From: "Paul Barker" <paul@pbarker.dev>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>, <yoann.congal@smile.fr>
Cc: "OE-core ML" <openembedded-core@lists.openembedded.org>,
<mark.hatle@amd.com>
Subject: Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
Date: Fri, 20 Nov 2026 11:12:08 +0000 [thread overview]
Message-ID: <DMZZRI421TEX.2ACT1HU5QSAM8@pbarker.dev> (raw)
In-Reply-To: <CANNYZj9Uj5v-Tb1TrA+TrxrdEyjO+qj25byZ0fWtUpiLHKH-DA@mail.gmail.com>
On Tue Nov 17, 2026 at 5:13 PM GMT, Alexander Kanavin wrote:
> On Tue, 17 Nov 2026 at 17:42, Yoann Congal via openembedded-core
> <yoann.congal=smile.fr@lists.openembedded.org> wrote:
>
>>
>> Pseudo now has a stable branch pseudo-1.9 with pseudo-1.9.x tags on it.
>
>
> Is this branch collecting only bugfixes (or fixes needed for continuing
> operation of yocto release branches)? Is this going to be a policy for any
> future point releases, or is it a one-off just for 1.9.x? There should be
> confirmation of these questions, in addition to the existence of the branch.
Hi Alex,
I think this is an overly pedantic interpretation of the policy for a
project where we control the upstream (pseudo). In this case, we should
be asking whether changes on pseudo 1.9.x are intended to be merged into
our YP stable branches (yes they are), how this affects stability
overall (in many ways, not taking pseudo changes has higher risk) and
whether the pseudo maintainers will be around to help if anything breaks
(yes they will be).
Making changes in pseudo is one the ways we keep up with changes in host
distros, not just with new host distro versions but with "fun" "stable"
changes like the tar CVE backport in RHEL derivatives at the start of
this year. So our stable branches have to be able to take new features
in pseudo.
If applying the upstream-stable-release-point bbclass helps with stable
maintenance of this recipe then we should do it.
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-11-20 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 16:41 [PATCH] pseudo: inherit upstream-stable-release-point Yoann Congal
2026-11-17 17:13 ` [OE-core] " Alexander Kanavin
2026-11-18 9:04 ` Yoann Congal
2026-11-18 10:55 ` Mark Hatle
2026-11-18 11:10 ` Alexander Kanavin
2026-11-18 14:23 ` Mark Hatle
2026-11-19 16:40 ` [yocto-patches] " Yoann Congal
2026-11-20 11:12 ` Paul Barker [this message]
2026-11-20 11:20 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DMZZRI421TEX.2ACT1HU5QSAM8@pbarker.dev \
--to=paul@pbarker.dev \
--cc=alex.kanavin@gmail.com \
--cc=mark.hatle@amd.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox