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 17 March 2026 ==
== Yocto Project Status 5 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-22<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 19th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 7th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 5th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Mar. 10am GMT and Monday 23rd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 7th May 10am GMT and Monday 11th 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 5.3.2 has been released
*YP 4.0.35 was released
*YP 6.0 M2 is due to be released
*YP 5.3.4 is due to release, pending TSC approval
*YP 4.0.34 is in QA.
*YP 6.0 is due to release, pending TSC approval
*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 due to build next week however there are many key changes needed still missing.
*Intermittent build failures continue to be problematic
*We have issues we need to resolve before M3:
*Patch review/merging is slow due to public holidays clashing with a review call
**x86 kvm seemingly broken with certain CPU features (#16074)
*Master is open for new development.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
*glibc was upgraded 2.43 and we released a new uninative to match
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
*We are adding testing of ptests on musl to our test matrix
*Kernel rust support has merged
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 47: Line 29:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2698 (last week 2788) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Total patches found: 1087 (last week 1085)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**Patches in the Pending State: 146 (13%) [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 M2 is ready for release.
*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 5.3.2 is released.
*YP 5.3.4 is due to release, pending TSC approval
*YP 4.0.34 is in QA.
*YP 5.0.18
*YP 5.3.3 is in QA.
**Build Date 2026-05-11
*YP 5.0.17 Build Date 2026-03-30
**Release Date 2026-05-25
*YP 5.0.17 Release Date 2026-04-15
*YP 6.0.1
*YP 4.0.35 Build Date 2026-04-06
**Build Date 2026-05-18
*YP 4.0.35 Release Date 2026-04-22
**Release Date 2026-06-01
*YP 5.3.4 Build Date 2026-04-20
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Revision as of 14:45, 5 May 2026

Yocto Project Status 5 May 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • YP 4.0.35 was released
  • YP 5.3.4 is due to release, pending TSC approval
  • YP 6.0 is due to release, pending TSC approval
  • 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
  • Patch review/merging is slow due to public holidays clashing with a review call
  • Master is open for new development.

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