Yocto Project Status 11 August 2026 (WW33)

Current Dev Position: YP 6.1 M3

Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

   -

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

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

   Yocto Project Patch Review - Thursday 13rd Aug. 10am GMT and Monday 17th
   Aug. 9am PDT (
   https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


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

Key Status/Updates:

   -

   YP 6.1 M2 has been released
   -

   YP 6.1 M3 is due in three weeks and this will be the feature freeze
   point for YP 6.1.
   -

   We would like to remind everyone that AI-generated code submitted to
   Yocto Project must include disclosure of the use of AI tools, in line with
   our policy in the contributor guide (
   https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code).
   Joshua has sent patches adding AGENTS.md <http://agents.md> files to
   bitbake and openembedded-core to prompt agents to follow this policy. We
   are discussing further updates to our policy on AI assisted submissions as
   this is a rapidly evolving area.
   -

   Alex Stewart is stepping down as maintainer of opkg - huge thanks to him
   for his work on the project over the last 5 years, and thanks to National
   Instruments/Emerson for their continued support of opkg. Maintainership is
   being handed over to Erick Shepherd (also from NI/Emerson), there is also a
   call for input and anyone interested in being a co-maintainer:
   https://lists.yoctoproject.org/g/opkg/topic/120687514
   -

   The NPM fetcher has been re-enabled in bitbake with security
   improvements and additional test cases
   -

   The upgrade to sbom-cve-check 1.3.3 has more correct handling of
   Ubuntu/Red Hat specific CVEs, which may require new patches or CVE_STATUS
   assignments. The fallout in OE-core has been handled, other layers may see
   an uptick in reported CVEs.
   -

   The SDK_TOOLCHAIN_LANGS variable has been replaced with a more general
   SDK_FEATURES variable to support improved SDK configurability. Uses of the
   old variable will need to be updated, `go` and `rust` langs are still
   supported as SDK features.
   -

   There are two AB-INT issues which are in a position where others could
   now help, as detailed in
   https://lists.openembedded.org/g/openembedded-core/message/242105:
   -

      Matchbox-wm segfault/xserver restart
      -

      aarch64/x86-64 build host contamination/reproducibility issue

We get a lot of comments about these being hard to reproduce or work on, in
both cases, these have specific well defined things which need to be done
and a basic understanding of what the issue relates to, if not the actual
fix.

   -

   Remaining intermittent build failures of concern:
   -

      other qemu ‘hang’ type issues on ARM
      -

      sometimes yocto-check-layer is showing checksum mismatch issues
      -

      intermittent ptest failures in many recipes


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 2694 (last week 2694) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1028 (last week 1029)
      -

      Patches in the Pending State: 139 (14%) [last week 141 (14%)]
      -

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


Upcoming development releases:

   -

   6.1 M2: is released,
   -

   6.1 M3:
   -

      Build Date: w/c 2026-08-31
      -

      Release Date: w/c 2026-09-14
      -

   6.1.0:
   -

      Build Date (M4): w/c 2026-10-12
      -

      Release Date: w/c 2026-11-02


Upcoming dot releases:

   -

   YP 6.0.3
   -

      Build Date w/c 2026-08-10
      -

      Release Date w/c 2026-08-24
      -

   YP 5.0.20
   -

      Build Date w/c 2026-08-17
      -

      Release Date w/c 2026-08-31
      -

   For future release dates, see
   https://wiki.yoctoproject.org/wiki/Release_calendar


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 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]>*