Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 14 April 2026 ==
== Yocto Project Status 28 July 2026 ==
Current Dev Position: YP 6.0 M4<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-20<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. 16th 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. 14th 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. 16th 10am GMT and Monday Apr. 20th 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.0.17 is due to be released
*YP 5.0.19 has been released
*YP 6.0 M3 is in QA
*YP 6.1 M2 is out of QA and under review
*YP 4.0.35 is queued for QA
*Progress has been made with some of the AB-INT issues:
*We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
**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
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Several pseudo issues were patched in a recent update
**Reports of pseudo errors on Fedora 44 beta related to openat2()
**One infrastructure issue on a worker was corrected
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
*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:
**Meta-oe cve layer filtering under new tooling (metrics script tweak?)
**Matchbox-wm segfault/xserver restart
**Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
**aarch64/x86-64 build host contamination/reproducibility issue
*There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.
    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.
git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*Some invasive LICENSE changes have merged into master:
*The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
**We now require the LICENSE field to match SPDX identifiers.  
*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 build will issue warnings when this isn’t the case.
*The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
*If you have any final patches for whinlatter, please get these sent to the list ASAP.
**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:'''<br/>
'''Ways to contribute:'''<br/>
Line 38: Line 48:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2777 (last week 2797) (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: 1072 (last week 1060)
**Total patches found: 1021 (last week 1019)
**Patches in the Pending State: 147 (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 in QA.
*6.1 M2: out of QA.
*YP 6.0 M4 Build Date 2026-04-13
**Release Date: w/c 2026-08-03
*YP 6.0 M4 Release Date 2026-05-04
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.17 is in review.
*YP 5.0.19 due to release
*YP 4.0.35 is in QA.
**Release Date w/c 2026-07-13
*YP 5.3.4
*YP 6.0.3
**Build Date 2026-04-20
**Build Date w/c 2026-08-10
**Release Date 2026-05-06
**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
*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"