Current Dev Position: YP 6.1 M2

Next Deadline: YP 6.1 M2: w/c 2026-07-20

Next Team Meetings:

   -

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

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

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


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

Key Status/Updates:

   -

   YP 6.0.2 has been released
   -

   YP 5.0.19 is due to release
   -

   YP 6.1 M2 will build this week after pseudo, systemd and resulttool
   changes merge
   -

   Some invasive LICENSE changes have merged into master:
   -

      We now require the LICENSE field to match SPDX identifiers.
      -

      The build will issue warnings when this isn’t the case.
      -

      Non SPDX licenses will need to be of the form LicenseRef-XXX
      -

      CLOSED is no longer a valid value.
      -

      ‘WITH’ license exceptions are now supported

Big thanks for Joshua for getting us to the point where we can finally
clean this up!

   -

   We have identified a few linux-yocto CVEs which need triaging due to
   missing version information in the CVE databases (affecting master, wrynose
   and scarthgap), see the email sent to the list:
   https://lists.yoctoproject.org/g/yocto/topic/120036383
   -

   Patches generated by the automatic upgrade helper (AUH) now include
   changelogs where these can be extracted from upstream.
   -

   A couple of further pseudo related issues were identified, one with
   linkat flags and one with openat2 (tar related/triggered). We hope to have
   patches merged soon.
   -

   Systemd issues with older host kernels (e.g. RHEL 8) is still being
   worked on
   https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
   -

   We’re working through the backlog of patches, the bandwidth for changes
   needing in depth review/feedback continues to be a challenge. The review
   calls are running out of time each meeting which limits progress.
   -

   We’re making little progress on intermittent build failures despite the
   problems continuing to impact test builds:
   -

      several qemu ‘hang’ type issues on ARM
      -

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

      siggen reset issues (“ResourceWarning: unclosed transport”)
      -

      groff build race issues
      -

      intermittent ptest failures in many recipes
      -

   For the qemuarmv5 amba crash (#16217
   <https://bugzilla.yoctoproject.org/show_bug.cgi?id=16217>), we did
   confirm it doesn’t seem to be load or memory usage related and does seem to
   happen on the autobuilder but not on other systems, for reasons still
   currently unknown.


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

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1019 (last week 1019)
      -

      Patches in the Pending State: 144 (14%) [last week 145 (14%)]
      -

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


Upcoming development releases:

   -

   6.1 M2:
   -

      Build Date: w/c 2026-07-20
      -

      Release Date: w/c 2026-08-03
      -

   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 5.0.19 due to release
   -

      Release Date w/c 2026-07-13
      -

   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]>*
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#241549): 
https://lists.openembedded.org/g/openembedded-core/message/241549
Mute This Topic: https://lists.openembedded.org/mt/120377976/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to