Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Status 3 March 2026 ==
== Yocto Project Status 12 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-09<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 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 14th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 12th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 14th May 10am GMT and Monday 18th May 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.33 has been released
*YP 5.3.4 is due to release (has been approved)
*YP 5.0.16 is in TSC review
*YP 6.0 is due to release (has been approved)
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
**We are aware of changes in QA timelines and are discussing how to address them.
*Intermittent build failures continue to be problematic
*We have issues which need further work that will block M3:
*We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
**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)
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**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.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!


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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2688 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 11063 (last week 1107)
**Total patches found: 1087 (last week 1087)
**Patches in the Pending State: 151 (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 in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.16 is in review.
*YP 5.3.4 is due to release
*YP 5.3.2 is in QA.
*YP 5.0.18
*YP 4.0.34 is in QA.
**Build Date 2026-05-11
*YP 5.3.3 Build Date 2026-03-09
**Release Date 2026-05-25
*YP 5.3.3 Release Date 2026-03-20
*YP 6.0.1
*YP 5.0.17 Build Date 2026-03-16
**Build Date 2026-05-18
*YP 5.0.17 Release Date 2026-03-23
**Release Date 2026-06-01
*YP 4.0.35 Build Date 2026-04-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*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:45, 12 May 2026

Yocto Project Status 12 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 5.3.4 is due to release (has been approved)
  • YP 6.0 is due to release (has been approved)
  • 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
  • We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
  • Master is open for new development
  • We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.

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