Weekly Status: Difference between revisions

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


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 21st May 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)
*Weekly Project Engineering Sync - Tuesday 19th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 2nd 10am GMT and Monday Apr. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 21st May 10am GMT and Monday 25th May 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 4.0.34 was released.
*YP 6.0 was released, thanks everyone who contributed!
*YP 5.3.3 is approved for release.
*YP 5.0.18 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Intermittent build failures continue to be problematic:
*Issues still pending:
**several qemu ‘hang’ type issues
**Splitting wic into an external tool.
**sometimes yocto-check-layer is showing checksum mismatch issues
**Converting scripts/run-cvecheck to sbom-cve-check
**siggen reset issues (“ResourceWarning: unclosed transport”)
**DISTRO_FEATURES defaults improvements.
**groff build race issues
**RHEL 9 xattrs/selinux/tar issue
**intermittent ptest failures in many recipes
**How to improve DEBUG_BUILD?
*Master (blacksail) is open for new development
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
*Issues that are mostly known quantities still needing work:
*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716
**x86 kvm seemingly broken with certain CPU features (#16074)
*Monday 25th May is a public holiday in the UK and USA so there will be no patch review call.
**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


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 46: Line 35:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2673 (last week 2688) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1062 (last week 1072)
**Total patches found: 1083 (last week 1087)
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
**Patches in the Pending State: 148 (14%) [last week 146 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
'''YP 6.0 Milestone Dates:'''<br/>
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.34 was released.
*YP 5.3.4 was released.
*YP 5.3.3 ready for release.
*YP 5.0.18 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 6.0.1
*YP 5.0.17 Release Date 2026-04-15
**Build Date 2026-05-18
*YP 4.0.35 Build Date 2026-04-06
**Release Date 2026-06-01
*YP 4.0.35 Release Date 2026-04-22
*YP 5.0.19
*YP 5.3.4 Build Date 2026-04-20
**Build Date 2026-06-30
*YP 5.3.4 Release Date 2026-05-06
**Release Date 2026-07-13
*YP 5.0.18 Build Date 2026-04-27
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Latest revision as of 14:47, 19 May 2026

Yocto Project Status 19 May 2026

Current Dev Position: YP 6.1 M1
Next Deadline: YP 6.1 M1: w/c 2026-06-08

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0 was released, thanks everyone who contributed!
  • YP 5.0.18 is in QA.
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
  • Intermittent build failures continue to be problematic:
    • several qemu ‘hang’ type issues
    • 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
  • Master (blacksail) is open for new development
  • We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
  • We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716
  • Monday 25th May is a public holiday in the UK and USA so there will be no patch review call.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming dot releases:

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=86830"