Yocto Project Status 6 January 2026 (WW01)
Stephen K Jolley <[email protected]>
| Newsgroups | org.yoctoproject.lists.yocto,org.openembedded.lists.openembedded-core,org.yoctoproject.lists.yocto-status |
|---|---|
| Message-ID | <CAK5yBb_UFZysYNDFjb247Ap7xEzwzEwY5ZRCfr1k19JaRnd90w@mail.gmail.com> |
Current Dev Position:YP 6.0 M1
Next Deadline: YP 6.0 M1 Build Date 2026-01-05
Next Team Meetings:
-
Bug Triage meeting - Thursday 8th Jan. 7:30am PDT (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
<https://zoom.us/j/990892712>
-
Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th
Jan. 9am PDT, then Monday 5th January 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.0.15 is in QA
-
YP 6.0 M1 will build when the 5 open high bugs are resolved.
-
We have a number of issues with build performance tests, test results
and hanging glibc NFS tests on the autobuilder which need to be resolved
before we can build a new release.
-
Due to the number of problems currently present, patch merging will have
to slow to avoid adding any further issues.
-
Yoann Congal is starting to ramp up as the new LTS maintainer to take
over from Steve Sakoman
-
The linux kernel is now defaulting to 6.18 and the other versions will
soon be removed.
-
We have isolated the Fedora43 workers until we can root cause the binary
problems it was causing when the sstate was shared to older systems
-
The project is exploring the idea of applying for funding for security
related work. If anyone (individual or consultancies) has ideas, please
talk to Paul/Richard/TSC. This is an opportunity to work on those issues
you never have time/funding for!
-
We will be entirely disabling the npm fetcher in bitbake due to the
security issues until those are resolved (
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105).
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
-
We have also started to identify inactive bugs which need retesting to
confirm if they still apply:
https://dashboard.yoctoproject.org/bugtriage/#retest-container
-
There are bugs that are currently unassigned for YP 6.0. See:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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 3011 (last week 2991) (
https://wiki.yoctoproject.org/charts/combo.html)
-
OE-Core/Poky Patch Metrics
-
Total patches found: 1092 (last week 1090)
-
Patches in the Pending State: 151 (14%) [last week 151 (14%)]
-
https://autobuilder.yocto.io/pub/non-release/patchmetrics/
YP 6.0 Milestone Dates:
-
YP 6.0 M1 Build Date 2026-01-05
-
YP 6.0 M1 Release Date 2026-01-16
-
YP 6.0 M2 Build Date 2026-02-02
-
YP 6.0 M2 Release Date 2026-02-13
-
YP 6.0 M3 Build Date 2026-03-02
-
YP 6.0 M3 Release Date 2026-03-13
-
YP 6.0 M4 Build Date 2026-03-30
-
YP 6.0 M4 Release Date 2026-04-26
Upcoming dot releases:.
-
YP 5.0.15 is in QA.
-
YP 5.3.1 Build Date 2026-01-12
-
YP 5.3.1 Release Date 2026-01-23
-
YP 4.0.33 Build Date 2026-01-26
-
YP 4.0.33 Release Date 2026-01-30
-
YP 5.0.16 Build Date 2026-02-09
-
YP 5.0.16 Release Date 2026-02-20
-
YP 5.3.2 Build Date 2026-02-16
-
YP 5.3.2 Release Date 2026-02-27
-
YP 4.0.34 Build Date 2026-02-23
-
YP 4.0.34 Release Date 2026-03-06
-
YP 5.3.3 Build Date 2026-03-09
-
YP 5.3.3 Release Date 2026-03-20
-
YP 5.0.17 Build Date 2026-03-16
-
YP 5.0.17 Release Date 2026-03-23
-
YP 4.0.35 Build Date 2026-04-06
-
YP 4.0.35 Release Date 2026-04-17
-
YP 5.3.4 Build Date 2026-04-13
-
YP 5.3.4 Release Date 2026-04-24
-
YP 5.0.18 Build Date 2026-04-20
-
YP 5.0.18 Release Date 2026-05-01
-
YP 5.0.19 Build Date 2026-05-26
-
YP 5.0.19 Release Date 2026-06-05
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]>*