Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: yoann.congal@smile.fr, yocto-patches@lists.yoctoproject.org,
	OE-core ML <openembedded-core@lists.openembedded.org>,
	mark.hatle@amd.com
Subject: Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
Date: Wed, 18 Nov 2026 08:23:43 -0600	[thread overview]
Message-ID: <8480f7e3-e306-4b7f-936c-44d55a87ba98@kernel.crashing.org> (raw)
In-Reply-To: <CANNYZj-QWR+BDPzG5b1sn2oKBjk0CzYEB8_KgyC32-QfPdkUhQ@mail.gmail.com>



On 11/18/26 5:10 AM, Alexander Kanavin wrote:
> The question is whether point releases of pseudo add only bugfixes? It's not 
> about 1.9 specifically, but any future release, e.g. 2.0.x as well.
> 
> The policy for what is acceptable is documented here:
> https://docs.yoctoproject.org/ref-manual/release-process.html#criteria-for-qualifying-upstreams <https://docs.yoctoproject.org/ref-manual/release-process.html#criteria-for-qualifying-upstreams>

That is the YP criteria, not pseudo's.  Pseudo criteria is do we need the patch 
in any particular version to deal with the hosts that we support in that 
version.  Support is very loosely defined for sure.

This is why I want to be clear they are separate projects, highly related of 
course, but separate.

There WILL be a 2,0 branch, once it's created.

As I said, work on master, backport to release branches to deal with issues on 
particular host types.

For example, pseudo-1.9 theoretically still supports MacOS/Darwin (it really 
doesn't but anyway), Master? We removed this code as it's known to not work, and 
there are no indications it's being used.  I'm not backporting that to 1.9, as 
it would be an API change.

--Mark

> Alex
> 
> On Wed, 18 Nov 2026 at 11:55, Mark Hatle <mark.hatle@kernel.crashing.org 
> <mailto:mark.hatle@kernel.crashing.org>> wrote:
> 
>     While pseudo is heavily driven by Yocto Project (and OpenEmbedded)
>     requirements,
>     I'm not treating this as a YP/OE specific project.
> 
>     When I say pseudo-1.9 has a stable API, I mean that.  The intention is that
>     development happens in master.  Stable branches can have backports, as
>     required/requested by contributors, but these backports need to "feel" stable,
>     have a stable API (don't change command line arguments, don't change system
>     requirements, etc.)
> 
>     Is there an official list of what is and isn't allowed no.  What pseudo does is
>     so specialized, I don't think I could come up with a documented set will and
>     won't.  I also don't expect any applications to write such a list as in the end
>     it is up to the contributors and maintainers to weigh each patch to
>     determine if
>     it feels appropriate to go on a stable branch.  But in practice I expect if
>     someone using pseudo-1.9 experiences breakage due to security fixes in an
>     existing platform release we'll backport the fixes there.  But I do not intend
>     to carry forward pseudo-1.9 forever and into newer host releases.
> 
>     So in short:
> 
>     1. New Development goes to master (or equivalent)
>     2. Backports from master to a numbered branch can be requested
>     3. Priority for backports will be given to resolve breaking issues in known
>     working hosts, generally centered around Yocto Project/OpenEmbedded as that is
>     our primary test vehicle.
>     4. We do not intend API changes to be backported to older version.  (It's not a
>     stronger statement, because with the security backports happening in
>     distributions, it might be required at some point.)
> 
>     --Mark
> 
>     On 11/17/26 11:13 AM, Alexander Kanavin via openembedded-core wrote:
>      > On Tue, 17 Nov 2026 at 17:42, Yoann Congal via openembedded-core
>      > <yoann.congal=smile.fr@lists.openembedded.org
>     <mailto:smile.fr@lists.openembedded.org>
>      > <mailto:smile.fr@lists.openembedded.org
>     <mailto: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.
>      >
>      > Alex
>      >
>      >
>      > -=-=-=-=-=-=-=-=-=-=-=-
>      > Links: You receive all messages sent to this group.
>      > View/Reply Online (#250463):
>     https://lists.openembedded.org/g/openembedded-core/message/250463
>     <https://lists.openembedded.org/g/openembedded-core/message/250463>
>      > Mute This Topic: https://lists.openembedded.org/mt/122316790/3616948
>     <https://lists.openembedded.org/mt/122316790/3616948>
>      > Group Owner: openembedded-core+owner@lists.openembedded.org
>     <mailto:openembedded-core%2Bowner@lists.openembedded.org>
>      > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
>     <https://lists.openembedded.org/g/openembedded-core/unsub>
>     [mark.hatle@kernel.crashing.org <mailto:mark.hatle@kernel.crashing.org>]
>      > -=-=-=-=-=-=-=-=-=-=-=-
>      >
> 

      reply	other threads:[~2026-11-18 14:23 UTC|newest]

Thread overview: 6+ 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 [this message]

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=8480f7e3-e306-4b7f-936c-44d55a87ba98@kernel.crashing.org \
    --to=mark.hatle@kernel.crashing.org \
    --cc=alex.kanavin@gmail.com \
    --cc=mark.hatle@amd.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    --cc=yocto-patches@lists.yoctoproject.org \
    /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