* [PATCH] pseudo: inherit upstream-stable-release-point
@ 2026-11-17 16:41 Yoann Congal
2026-11-17 17:13 ` [OE-core] " Alexander Kanavin
0 siblings, 1 reply; 7+ messages in thread
From: Yoann Congal @ 2026-11-17 16:41 UTC (permalink / raw)
To: OE-core ML; +Cc: Yoann Congal
From: Yoann Congal <yoann.congal@smile.fr>
Pseudo now has a stable branch pseudo-1.9 with pseudo-1.9.x tags on it.
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
---
meta/recipes-devtools/pseudo/pseudo.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/pseudo/pseudo.inc b/meta/recipes-devtools/pseudo/pseudo.inc
index ba946ef9c97..dabf7a63007 100644
--- a/meta/recipes-devtools/pseudo/pseudo.inc
+++ b/meta/recipes-devtools/pseudo/pseudo.inc
@@ -19,7 +19,7 @@ PROVIDES += "virtual/fakeroot"
MAKEOPTS = ""
MAKEOPTS:class-native = "'RPATH=-Wl,--rpath=XORIGIN/../../../sqlite3-native/usr/lib/'"
-inherit siteinfo pkgconfig
+inherit siteinfo pkgconfig upstream-stable-release-point
do_configure () {
:
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
2026-11-17 16:41 [PATCH] pseudo: inherit upstream-stable-release-point Yoann Congal
@ 2026-11-17 17:13 ` Alexander Kanavin
2026-11-18 9:04 ` Yoann Congal
2026-11-18 10:55 ` Mark Hatle
0 siblings, 2 replies; 7+ messages in thread
From: Alexander Kanavin @ 2026-11-17 17:13 UTC (permalink / raw)
To: yoann.congal; +Cc: OE-core ML, mark.hatle
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
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.
Alex
[-- Attachment #2: Type: text/html, Size: 840 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
2026-11-17 17:13 ` [OE-core] " Alexander Kanavin
@ 2026-11-18 9:04 ` Yoann Congal
2026-11-18 10:55 ` Mark Hatle
1 sibling, 0 replies; 7+ messages in thread
From: Yoann Congal @ 2026-11-18 9:04 UTC (permalink / raw)
To: Alexander Kanavin; +Cc: OE-core ML, mark.hatle
On Tue Nov 17, 2026 at 6:13 PM CET, 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.
>
> Alex
Hello,
Good point.
The best we have right now is this:
https://lore.kernel.org/all/1783104055-19005-1-git-send-email-mark.hatle@kernel.crashing.org/
> (I have already created a pseudo-1.9 branch so we can backport stable
> changes as needed.)
Which is a bit terse...
As nothing about this is urgent nor critical, I've created a bug:
16529 – Document pseudo stable policy (1.9.x)
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16529
... so it can be treated at the right time.
As for this patch, let's hold it until the policy has been cleared up.
Regards,
--
Yoann Congal
Smile ECS
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
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
1 sibling, 1 reply; 7+ messages in thread
From: Mark Hatle @ 2026-11-18 10:55 UTC (permalink / raw)
To: alex.kanavin, yoann.congal, yocto-patches; +Cc: OE-core ML, mark.hatle
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>> 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
> Mute This Topic: https://lists.openembedded.org/mt/122316790/3616948
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [mark.hatle@kernel.crashing.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
2026-11-18 10:55 ` Mark Hatle
@ 2026-11-18 11:10 ` Alexander Kanavin
2026-11-18 14:23 ` Mark Hatle
0 siblings, 1 reply; 7+ messages in thread
From: Alexander Kanavin @ 2026-11-18 11:10 UTC (permalink / raw)
To: Mark Hatle; +Cc: yoann.congal, yocto-patches, OE-core ML, mark.hatle
[-- Attachment #1: Type: text/plain, Size: 3203 bytes --]
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
Alex
On Wed, 18 Nov 2026 at 11:55, Mark Hatle <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>> 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
> > Mute This Topic: https://lists.openembedded.org/mt/122316790/3616948
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> mark.hatle@kernel.crashing.org]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>
[-- Attachment #2: Type: text/html, Size: 4608 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
2026-11-18 11:10 ` Alexander Kanavin
@ 2026-11-18 14:23 ` Mark Hatle
2026-11-19 16:40 ` [yocto-patches] " Yoann Congal
0 siblings, 1 reply; 7+ messages in thread
From: Mark Hatle @ 2026-11-18 14:23 UTC (permalink / raw)
To: Alexander Kanavin; +Cc: yoann.congal, yocto-patches, OE-core ML, mark.hatle
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>]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [yocto-patches] [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
2026-11-18 14:23 ` Mark Hatle
@ 2026-11-19 16:40 ` Yoann Congal
0 siblings, 0 replies; 7+ messages in thread
From: Yoann Congal @ 2026-11-19 16:40 UTC (permalink / raw)
To: yocto-patches, Alexander Kanavin; +Cc: OE-core ML, mark.hatle
On Wed Nov 18, 2026 at 3:23 PM CET, Mark Hatle via yocto-patches wrote:
> 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
(Sorry, I kinda feel I kicked a hornet's nest here. I did not intended
to)
I'll drop my patch. The policy you describe is not compatible with
"inherit upstream-stable-release-point" and this is absolutely fine.
It just mean I'll continue to upgrades like I was doing before.
Regards,
>
>> 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 (#5472): https://lists.yoctoproject.org/g/yocto-patches/message/5472
> Mute This Topic: https://lists.yoctoproject.org/mt/122329726/4316185
> Group Owner: yocto-patches+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13179410/4316185/929767106/xyzzy [yoann.congal@smile.fr]
> -=-=-=-=-=-=-=-=-=-=-=-
--
Yoann Congal
Smile ECS
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2026-11-19 16:40 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox