Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 27th, 2026 ==
== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 6.0 M1<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-02<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>
6
 
'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 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.15 was released
*YP 6.0 M2 has been released.
* YP 5.3.1 is under review
*YP 4.0.34 is due to be released.
* YP 6.0 M1 is in QA
*YP 5.3.3 is in review after QA.
* YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
* YP 6.0 M2 is due next week!
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.  
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
**Issues still pending:
* There are currently 6 high open bugs, which will block M2:
**Splitting wic into an external tool.
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
** x86 kvm broken on Fedora 43 (#16074)
**How to improve DEBUG_BUILD?
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
**DISTRO_FEATURES defaults improvements.
** Hangs of the autobuilder controller (database locking?) (#16129)
**SBOM/cve-check changes.
** Generation of releases.json needs updating (#16138)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Issues that are mostly known quantities still needing work:
* Patches are merging again 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.
**x86 kvm seemingly broken with certain CPU features (#16074)
 
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*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.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 37: Line 45:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
* WDD 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
**Total patches found: 1069 (last week 1081)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**Patches in the Pending State: 152 (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-02
*YP 6.0 M2 was released.
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-05-04
*YP 6.0 M4 Release Date 2026-04-26
 


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.3.1 is under review.
*YP 4.0.34 ready for release.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.3.3 is in review.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.16 Release Date 2026-02-20
*YP 5.0.17 Release Date 2026-04-15
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*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 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-04-24
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05
*YP 5.0.19 Release Date 2026-06-05

Latest revision as of 14:43, 24 March 2026

Yocto Project Status 24 March 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0 M2 has been released.
  • YP 4.0.34 is due to be released.
  • YP 5.3.3 is in review after QA.
  • YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
  • YP 6.0 M3 is now due to build however there are many key changes needed still missing.
    • Issues still pending:
    • Splitting wic into an external tool.
    • Deprecation of ltp (upstream dropped runltp and mandate kirk)
    • How to improve DEBUG_BUILD?
    • DISTRO_FEATURES defaults improvements.
    • SBOM/cve-check changes.
    • AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
  • Issues that are mostly known quantities still needing work:
    • x86 kvm seemingly broken with certain CPU features (#16074)
    • Failure to generate regression reports in release builds
    • Reconcile poky and OE-Core defaults templates.
    • Resolve Fedora 43 selftest failures
    • Fixing yocto-check-layer to work with –machines
  • Issues that were resolved this week:
    • Switching to pkg-config.
    • Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
  • We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
  • 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.

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M2 was released.
  • 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:

  • YP 4.0.34 ready for release.
  • YP 5.3.3 is in review.
  • YP 5.0.17 Build Date 2026-03-30
  • YP 5.0.17 Release Date 2026-04-15
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-22
  • YP 5.3.4 Build Date 2026-04-20
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives

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