Yocto Project Status 21 October 2025 (WW42)

Stephen K Jolley <[email protected]> Tue, 21 Oct 2025 07:36:24 -0700

Newsgroups	org.yoctoproject.lists.yocto,org.openembedded.lists.openembedded-core,org.yoctoproject.lists.yocto-status
Message-ID	<CAK5yBb8BPU8gQp3+c8dD5dqod7fY2z+np3JjBSeTtfCx21NxLQ@mail.gmail.com>

Current Dev Position: YP 5.3 M3

Next Deadline: YP 5.3 M3 Build Date 2025-09-01

Next Team Meetings:

Bug Triage meeting - Thursday Oct. 23rd 7:30 am PDT (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-

Weekly Project Engineering Sync - Tuesday Oct. 21st 8 am PDT (
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
<https://zoom.us/j/990892712>
-

Yocto Project Patch Review - Thursday Oct. 23rd 10am GMT and Monday
Oct. 27th 9am PDT (
https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
<https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>)

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

YP 5.3 M3 and 5.0.13 currently in QA.
-

YP 5.2.4 has been released
-

We’re at feature freeze for YP 5.3. Patches that will be accepted now
have a higher bar until after we branch master from whinlatter. Known
issues:
-

check-layer tests are now running under nodistro instead of poky, so
some layers are failing as they assume some DISTRO_FEATURES are enabled.
-

Toaster is broken with bitbake-setup (#16012). Help moving to
supporting non-poky layouts would be good if anyone is using Toaster.
-

The patch/cve metrics jobs need reviewing to be sure they’re correct
with bitbake-setup (#16013)
-

The build performance jobs don’t know that poky and oe-core are the
same so the charts are currently wrong (#16014)
-

Help welcomed to resolve this issues!
-

Rust now reuses the same LLVM as Clang, and the rust-llvm recipe has
been deleted. Many thanks to Deepesh and others at Wind River!. There’s a
known regression building rust with clang which is being investigated.
-

Upstream kernel just end-of-life’d 6.16 but whinlatter will ship with
6.16. It’s probably too late to upgrade to 6.17 for the release, we’ll have
to see as to whether we upgrade post-release.
-

“poky” as a combo-layer repository will soon no longer be needed or
updated for master and whinlatter branches.
-

There are likely going to be breaking changes to the npm fetcher related
to ongoing security concerns.

Ways to contribute:

As people are likely aware, the project has a number of components which
are either unmaintained, or have people with little to no time trying to
keep them alive. These components include: devtool, toaster, wic, oeqa,
autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help
is welcome in trying to better look after these components!
-

There is an issue open upstream with the openssl project related to
making path relocation of openssl easier (as used in our buildtools tarball
and SDK). We’d love assistance in moving this forward and getting some kind
of upstream feature merged to make this easier:
https://github.com/openssl/openssl/pull/19260
-

There are bugs identified as possible for newcomers to the project:
https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
-

There are bugs that are currently unassigned for YP 5.3. See:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
-

We’d welcome new maintainers for recipes in OE-Core. Please see the list
at:
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
and discuss with the existing maintainer, or ask on the OE-Core mailing
list. We will likely move a chunk of these to “Unassigned” soon to help
facilitate this.
-

Help is very much welcome in trying to resolve our autobuilder
intermittent issues. You can see the list of failures we’re continuing to
see by searching for the “AB-INT” tag in bugzilla:
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
-

Help us resolve CVE issues: CVE metrics
<https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
-

We have a growing number of bugs in bugzilla, any help with them is
appreciated.
-

Regarding bugs, even if you can’t fix a bug, submitting a failing test
case that can reproduce the issue significantly improves the chances it
might get fixed.
-

Further help on optimizing build disk usage would be most welcome.
-

Ongoing project development plans are being developed in this document:
https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing

We need to continue to develop this as it will allow us to potentially find
ways to fund specific work items.

Tracking Metrics:

WDD 3009 (last week 2904) (
https://wiki.yoctoproject.org/charts/combo.html)
-

OE-Core/Poky Patch Metrics
-

Total patches found: 1091 (last week 1096)
-

Patches in the Pending State: 153 (14%) [last week 154 (14%)]
-

https://autobuilder.yocto.io/pub/non-release/patchmetrics/

YP 5.3 Milestone Dates:

YP 5.3 M3 is in QA.
-

YP 5.3 M4 Build Date 2025-10-06
-

YP 5.3 M4 Release Date 2025-10-31

Upcoming dot releases:.

YP 5.2.4 was released.
-

YP 5.0.13 is in QA.
-

YP 4.0.31 Build Date 2025-11-03
-

YP 4.0.31 Release Date 2025-11-14
-

YP 5.0.14 Build Date 2025-11-17
-

YP 5.0.14 Release Date 2025-11-28
-

YP 4.0.32 Build Date 2025-12-15
-

YP 4.0.32 Release Date 2025-12-24
-

YP 5.0.15 Build Date 2026-01-05
-

YP 5.0.15 Release Date 2026-01-16

The Yocto Project’s technical governance is through its Technical Steering
Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this
weekly status update, let us know!]

Thanks,

*Stephen K. Jolley*

*Yocto Project Program Manager*

( *Cell*: (208) 244-4460

* *Email*: *s
<[email protected]>[email protected] <[email protected]>*