Yocto Project Status 31 March 2026 (WW14)

Yocto Project Status 31 March 2026 (WW14)

[Stephen K Jolley]

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

Current Dev Position: YP 6.0 M3

Next Deadline: YP 6.0 M3 Build Date 2026-03-23

Next Team Meetings:

   -

   Bug Triage meeting - Thursday 2nd Apr. 7:30am PDT (
   https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
   -

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

   Yocto Project Patch Review - Thursday 2nd Apr. 10am GMT and Monday 6th
   Apr. 9am PDT (https://zoom.us/j/9776239
   <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>7
   148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
   <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>)


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

Key Status/Updates:

   -

   YP 4.0.34 was released.
   -

   YP 5.3.3 is approved for release.
   -

   YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
   -

   YP 6.0 M3 is now due to build however there are still key changes
   missing.
   -

   Issues still pending:
   -

      Splitting wic into an external tool.
      -

      Converting scripts/run-cvecheck to sbom-cve-check
      -

      DISTRO_FEATURES defaults improvements.
      -

      RHEL 9 xattrs/selinux/tar issue
      -

      How to improve DEBUG_BUILD?
      -

      RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
      -

   Issues that are mostly known quantities still needing work:
   -

      x86 kvm seemingly broken with certain CPU features (#16074
      <https://bugzilla.yoctoproject.org/show_bug.cgi?id=16074>)
      -

      Failure to generate regression reports in release builds
      -

      Fixing yocto-check-layer to work with --machines (many fixes merged)
      -

   Issues that were resolved this week:
   -

      Sbom-cve-check added
      -

      Replacement of runtlp with kirk (Thanks Daniel!)
      -

      bitbake-setup vscode integration
      -

      Fedora 43 selftest failures
      -

      Reconciling poky and OE-Core defaults templates.
      -

   We have rationalized the tags in various project repositories, more
   information can be found here:
   https://lists.openembedded.org/g/openembedded-architecture/message/2312
   Whilst controversial, this will make the tag list much easier to understand
   for users, guide users to use the right tags going forward and remove
   confusion about whether any tags were “missed”, at the expense that some CI
   setups may need adjusting short term.
   -

   We’re working through the backlog of patches and intermittent build
   failures are still problematic, including the emergence of new issues
   (newer kernel version?). We continue to struggle for bandwidth for changes
   needing in depth review/feedback. This could impact features making it into
   the LTS.
   -

   The CFP closing date for the Yocto Project Workshop at Embedded Recipes
   2026 has been extended until April 7th, please submit a proposal if you’d
   like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp


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

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1062 (last week 1072)
      -

      Patches in the Pending State: 148 (14%) [last week 151 (14%)]
      -

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


YP 6.0 Milestone Dates:

   -

   YP 6.0 M3 Build Date  2026-03-23
   -

   YP 6.0 M3 Release Date 2026-04-08
   -

   YP 6.0 M4 Build Date 2026-04-13
   -

   YP 6.0 M4 Release Date 2026-05-04


Upcoming dot releases:

   -

   YP 4.0.34 was released.
   -

   YP 5.3.3  is approved for release.
   -

   YP 5.0.17 Build Date 2026-03-30
   -

   YP 5.0.17 Release Date 2026-04-15
   -

   YP 4.0.35 Build Date 2026-04-06
   -

   YP 4.0.35 Release Date 2026-04-22
   -

   YP 5.3.4 Build Date  2026-04-20
   -

   YP 5.3.4 Release Date 2026-05-06
   -

   YP 5.0.18 Build Date 2026-04-27
   -

   YP 5.0.18 Release Date 2026-05-13
   -

   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
<stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com <jolley.yp.pm@gmail.com>*

[-- Attachment #2: Type: text/html, Size: 49949 bytes --]

Re: [yocto] Yocto Project Status 31 March 2026 (WW14)

[Paul Barker]

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

On Tue, 2026-03-31 at 07:50 -0700, Stephen Jolley via
lists.yoctoproject.org wrote:
> Current Dev Position: YP 6.0 M3
> 
> Next Deadline: YP 6.0 M3 Build Date 2026-03-23
> 
> Next Team Meetings:
> 
>    -
> 
>    Bug Triage meeting - Thursday 2nd Apr. 7:30am PDT (
>    https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
>    -
> 
>    Weekly Project Engineering Sync  - Tuesday 31st Mar. 8am PDT (
>    https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
>    <https://zoom.us/j/990892712>
>    -
> 
>    Yocto Project Patch Review - Thursday 2nd Apr. 10am GMT and Monday 6th
>    Apr. 9am PDT (https://zoom.us/j/9776239
>    <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>7
>    148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
>    <https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1>)

Hi all,

Monday 6th April is a public holiday here in the UK so Ross, Richard and
myself will all be out of office. So, there will be no patch review call
on Monday!

Best regards,

-- 
Paul Barker


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

Re: [yocto-status] [yocto] Yocto Project Status 31 March 2026 (WW14)

[Paul Barker]

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

On Tue, 2026-03-31 at 15:58 -0400, Walt Miner via lists.yoctoproject.org
wrote:
> When will we see the plan for after June 5?

Hi Walt,

This is on me. I have provisional dates, I need to make sure they're ok
then get them sent to the list. I've been focused on blocking issues for
the 6.0 M3 build but should get to this later this week.

Best regards,

-- 
Paul Barker


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