Yocto Project Status 24 February 2026 (WW09)

Yocto Project Status 24 February 2026 (WW09)

[Paul Barker]

[-- Attachment #1: Type: text/plain, Size: 5327 bytes --]

Hi all,

Current Dev Position: YP 6.0 M2
Next Deadline: YP 6.0 M2 Build Date 2026-02-16

Next Team Meetings:
- Bug Triage meeting - Thursday 26th Feb. 7:30am PDT
  (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Weekly Project Engineering Sync  - Tuesday 24th Feb. 8am PDT
  (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am
  (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

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

Key Status/Updates:
- YP 4.0.33 is due for release
- YP 5.0.16 is in QA
- YP 5.2.3 is queued for QA
- YP 6.0 M2 is due to build when we have patches merged
- We have two open high issues which need further work that will block M3: 
    - x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
    - AB-INT: opkg-build segmentation fault (memory corruption in
      pseudo?) (#16078)
- We also have issues we need to resolve before release:
    - Allowing non-destructive git fetcher updates for bitbake-setup
    - Splitting wic into an external tool
    - Kernel rust support
    - Switching to pkg-config
    - Deprecation of ltp (upstream dropped runltp and mandate kirk)
    - How to improve DEBUG_BUILD?
    - DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
    - SBOM/cve-check changes
- We updated “nodistro” to use 3 of the include files poky was already
  using:
    - Space optimization to reduce build footprint and sstate object
      size
    - Disabling most static libraries by default (build size/speed wins)
    - Enabling security flags by default
- “nodistro” now also enables uninative by default to allow for better
  CDN sstate reuse
- Distros now need to use INIT_MANAGER to select their preferred init
  system with the default being systemd for “nodistro”. Poky’s defaults
  remain unchanged and we don’t have plans to change this at this time
  due to the work involved and impact (e.g test result comparisons).
- The number of intermittent failures affecting builds, both stable and
  development, continues to be problematic - we continue to prioritise
  addressing these since any given build is now statistically likely to
  hit one or more of them.
- Patches are merging but there is a backlog and we’ve had to prioritize
  simpler changes. We continue to struggle for bandwidth for changes
  needing in depth review/feedback. This could impact features making it
  into the LTS.

Want to contribute? We would appreciate help with the following areas:
- We have several open issues for pseudo and limited maintainer time to
  work on them. Help from someone familiar with systems programming in C
  would be greatly appreciated.
  https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
- There are a large number of intermittent failures on our autobuilder,
  any help with investigating, reproducing or solving these issues would
  be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
- Many recipes in openembedded-core would benefit from a new recipe
  maintainer. Please look at
  https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc
  and see if you can adopt any of the unassigned recipes.
- For more ways to contribute, see
  https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

New to the project?
- We have a list of issues we think are good places to start
  contributing:
  https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

Tracking Metrics:
- WDD 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
- OE-Core/Poky Patch Metrics
    - Total patches found: 1108 (last week 1106)
    - Patches in the Pending State: 151 (14%) [last week 152 (14%)]
    - https://valkyrie.yocto.io/pub/non-release/patchmetrics/

YP 6.0 Milestone Dates:
- YP 6.0 M2 Build Date 2026-02-16
- YP 6.0 M2 Release Date 2026-02-27
- YP 6.0 M3 Build Date 2026-03-09
- YP 6.0 M3 Release Date 2026-03-20
- YP 6.0 M4 Build Date 2026-03-30
- YP 6.0 M4 Release Date 2026-04-26

Upcoming dot releases:
- YP 5.0.16 Release Date 2026-02-20
- 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!]

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: Yocto Project Status 24 February 2026 (WW09)

[Paul Barker]

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

On Tue, 2026-02-24 at 15:28 +0000, Paul Barker wrote:
> Key Status/Updates:
> - YP 4.0.33 is due for release
> - YP 5.0.16 is in QA
> - YP 5.2.3 is queued for QA

5.3.2, not 5.2.3, obviously. Thanks Peter for catching this and letting
me know!

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]