Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 7 April 2026 ==
== Yocto Project Status 28 July 2026 ==
Current Dev Position: YP 6.0 M3<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Apr. 9th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 30th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 7th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 28th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 9th 10am GMT and Monday Apr. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 30th July 10am GMT and Monday 3rd Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.3.3 was released.
*YP 5.0.19 has been released
*YP 5.0.17 is in QA
*YP 6.1 M2 is out of QA and under review
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*Progress has been made with some of the AB-INT issues:
*YP 6.0 M3 is now due to build however there are still key changes missing.
**We identified a kernel issue likely causing the arm psplash boot hangs
*Issues with pending work needed:
**The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
**Converting scripts/run-cvecheck to sbom-cve-check
**Several pseudo issues were patched in a recent update
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**One infrastructure issue on a worker was corrected
**Failure to generate regression reports in release builds (need tags)
*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:
**Ubuntu 26.04 support (need worker adding for testing)
**Matchbox-wm segfault/xserver restart
*Issues that have patches ready to merge:
**aarch64/x86-64 build host contamination/reproducibility issue
**DISTRO_FEATURES defaults improvements.
    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.
**Fixing yocto-check-layer to work with --machines
*Some invasive LICENSE changes have merged into master:
**RHEL 9 xattrs/selinux/tar issue
**We now require the LICENSE field to match SPDX identifiers.  
**Splitting wic into an external tool.
**The build will issue warnings when this isn’t the case.
**RHEL 10/openSUSE Leap 16.0 support
**Non SPDX licenses will need to be of the form LicenseRef-XXX
*Issues that need investigation
**CLOSED is no longer a valid value.
**Reports of pseudo errors on Fedora 44 beta
**‘WITH’ license exceptions are now supported
*The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
Big thanks to Joshua for getting us to the point where we can finally clean this up!
*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.
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
*We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
*We continue to work on the backlog of patches which has slightly reduced.
*The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp
*Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
*Remaining intermittent build failures  of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**intermittent ptest failures in many recipes


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 43: Line 48:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2797 (last week 2814) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2689 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1062)
**Total patches found: 1021 (last week 1019)
**Patches in the Pending State: 148 (14%) [last week 148 (14%)]
**Patches in the Pending State: 141 (14%) [last week 144 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 6.0 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 6.0 M3 Build Date 2026-03-23
*6.1 M2: out of QA.
*YP 6.0 M3 Release Date 2026-04-08
**Release Date: w/c 2026-08-03
*YP 6.0 M4 Build Date 2026-04-13
*6.1 M3:
*YP 6.0 M4 Release Date 2026-05-04
**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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.3.3 was released.
*YP 5.0.19 due to release
*YP 5.0.17 is in QA.
**Release Date w/c 2026-07-13
*YP 4.0.35
*YP 6.0.3
**Build Date 2026-04-06
**Build Date w/c 2026-08-10
**Release Date 2026-04-22
**Release Date w/c 2026-08-24
*YP 5.3.4
*YP 5.0.20
**Build Date 2026-04-20
**Build Date w/c 2026-08-17
**Release Date 2026-05-06
**Release Date w/c 2026-08-31
 
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


Latest revision as of 14:48, 28 July 2026

Yocto Project Status 28 July 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.19 has been released
  • YP 6.1 M2 is out of QA and under review
  • Progress has been made with some of the AB-INT issues:
    • We identified a kernel issue likely causing the arm psplash boot hangs
    • The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
    • Several pseudo issues were patched in a recent update
    • One infrastructure issue on a worker was corrected
  • 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.
  • 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 to Joshua for getting us to the point where we can finally clean this up!

  • Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
  • We continue to work on the backlog of patches which has slightly reduced.
  • Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2: out of QA.
    • 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

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86857"