Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
m (5.2.3 -> 5.3.2)
Line 1: Line 1:
== Yocto Project Status 24 February 2026 ==
== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M2<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-09<br/>


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


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.33 is due for release
*YP 4.0.33 has been released
*YP 5.0.16 is in QA
*YP 5.0.16 is in TSC review
*YP 5.3.2 is queued for QA
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
*YP 6.0 M2 is due to build when we have patches merged
**We are aware of changes in QA timelines and are discussing how to address them.
*We have two open high issues which need further work that will block M3:  
*We have issues which need further work that will block M3:  
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool
**Splitting wic into an external tool.
**Kernel rust support
**Kernel rust support.
**Switching to pkg-config
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes
**SBOM/cve-check changes.
*We updated “nodistro” to use 3 of the include files poky was already using:
**Reconcile poky and OE-Core defaults templates.
**Space optimization to reduce build footprint and sstate object size
*OE-Core switched to enabling a hash equivalence server by default.
**Disabling most static libraries by default (build size/speed wins)
*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.
**Enabling security flags by default
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.


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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Total patches found: 11063 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**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 Milestone Dates:'''<br/>
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 is in QA.
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M3 Release Date 2026-03-20
Line 61: Line 57:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.16 Release Date 2026-02-20
*YP 5.0.16 is in review.
*YP 5.3.2 Release Date 2026-02-27
*YP 5.3.2 is in QA.
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 is in QA.
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.3.3 Release Date 2026-03-20

Revision as of 15:55, 3 March 2026

Yocto Project Status 3 March 2026

Current Dev Position: YP 6.0 M3
Next Deadline: YP 6.0 M3 Build Date 2026-03-09

Next Team Meetings:

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

Key Status/Updates:

  • YP 4.0.33 has been released
  • YP 5.0.16 is in TSC review
  • YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
    • We are aware of changes in QA timelines and are discussing how to address them.
  • We have issues which need further work that will block M3:
    • x86 kvm seemingly broken with certain CPU features (#16074)
    • AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
    • 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:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • 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:

  • YP 5.0.16 is in review.
  • YP 5.3.2 is in QA.
  • YP 4.0.34 is in QA.
  • YP 5.3.3 Build Date 2026-03-09
  • YP 5.3.3 Release Date 2026-03-20
  • YP 5.0.17 Build Date 2026-03-16
  • YP 5.0.17 Release Date 2026-03-23
  • YP 4.0.35 Build Date 2026-04-06
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives

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