[meta-swupdate] scarthgap branch

[Marko, Peter]

Hello Stefano,

 

I’d like to clarify status of branch scarthgap of meta-swupdate.

I’d expect that it follows LTS strategy of yocto/oe:

https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#Stable/LTS_Patch_Acceptance_Policies

However, it backports almost everything from master branch, including breaking changes.

 

Couple days ago, following commit hit scarthgap:

https://github.com/sbabic/meta-swupdate/commit/2b48267fcfedf61c2a33c7830e794115263639f8

This removes all swupdate versions older than 2025, so everything which was available when scarthgap was created.

Meaning meta-layer update forces me to add years of breaking changes, definitely not a commit for an LTS branch.

 

I’m used to update all my meta layers when new oe-core tag is available, but meta-swupdate is the only one where it’s not feasible.

Could you elaborate a bit what this branch is about?

I’m willing to submit patches to remove breaking changes, but I need to know the direction first…

 

Thank you,

  Peter

[Stefano Babic]

Hi Peter,

On 12/10/25 22:29, 'Marko, Peter' via swupdate wrote:
> Hello Stefano,
>
> I’d like to clarify status of branch scarthgap of meta-swupdate.
>
> I’d expect that it follows LTS strategy of yocto/oe:
>
> https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#Stable/

> LTS_Patch_Acceptance_Policies <https://wiki.yoctoproject.org/wiki/
> Stable_Release_and_LTS#Stable/LTS_Patch_Acceptance_Policies>

>
> However, it backports almost everything from master branch, including
> breaking changes.
>
> Couple days ago, following commit hit scarthgap:
>
> https://github.com/sbabic/meta-swupdate/

> commit/2b48267fcfedf61c2a33c7830e794115263639f8 <https://github.com/
> sbabic/meta-swupdate/commit/2b48267fcfedf61c2a33c7830e794115263639f8>

>
> This removes all swupdate versions older than 2025, so everything which
> was available when scarthgap was created.

mmmhhh....yes, this is unwanted.

Different as YP, I provide update for SWUpdate in LTS version, that
means 2025.12 is then supported. But previous versions should be removed
only from master. Integrator should then set PREFERRED_VERSION_swupdate
if he will to stick with one version.

>
> Meaning meta-layer update forces me to add years of breaking changes,
> definitely not a commit for an LTS branch.
>
> I’m used to update all my meta layers when new oe-core tag is available,
> but meta-swupdate is the only one where it’s not feasible.
>
> Could you elaborate a bit what this branch is about?
>
> I’m willing to submit patches to remove breaking changes, but I need to
> know the direction first…

Yes, please do it.

Best regards,
Stefano