Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(21 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Status 24 February 2026 ==
== Yocto Project Status 30 June 2026 ==
Current Dev Position: YP 6.0 M2<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<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 2nd July 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 30th June 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 2nd July 10am GMT and Monday 6th July 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.33 is due for release
*YP 6.1 M1 was released
*YP 5.0.16 is in QA
*YP 6.0.2 is in QA
*YP 5.2.3 is queued for QA
*The number of open CVEs on scarthgap has been reduced with stable kernel updates merging. We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases, see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*YP 6.0 M2 is due to build when we have patches merged
*Systemd v260+ will require a host Linux kernel of 5.10 or later due to systemd utils run during the build process. This presents issues with RHEL 8 era distros which have older kernel versions. We have patches in progress but if you’re using these distros, assistance will be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We have two open high issues which need further work that will block M3:  
*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Intermittent build failures continue to be problematic:
*We also have issues we need to resolve before release:
**several qemu ‘hang’ type issues
**Allowing non-destructive git fetcher updates for bitbake-setup
**sometimes yocto-check-layer is showing checksum mismatch issues
**Splitting wic into an external tool
**siggen reset issues (“ResourceWarning: unclosed transport”)
**Kernel rust support
**groff build race issues
**Switching to pkg-config
**intermittent ptest failures in many recipes
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
*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
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“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 35:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2647 (last week 2620) (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: 1036 (last week 1054)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**Patches in the Pending State: 145 (14%) [last week 145 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 6.0 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 6.0 M2 Build Date 2026-02-16
*6.1 M2:
*YP 6.0 M2 Release Date 2026-02-27
**Build Date: w/c 2026-07-20
*YP 6.0 M3 Build Date 2026-03-09
**Release Date: w/c 2026-08-03
*YP 6.0 M3 Release Date 2026-03-20
*6.1 M3:
*YP 6.0 M4 Build Date 2026-03-30
**Build Date: w/c 2026-08-31
*YP 6.0 M4 Release Date 2026-04-26
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.16 Release Date 2026-02-20
*YP 5.0.19
*YP 5.3.2 Release Date 2026-02-27
**Build Date w/c 2026-06-30
*YP 4.0.34 Build Date 2026-02-23
**Release Date w/c 2026-07-13
*YP 4.0.34 Release Date 2026-03-06
*YP 6.0.3
*YP 5.3.3 Build Date 2026-03-09
**Build Date w/c 2026-08-10
*YP 5.3.3 Release Date 2026-03-20
**Release Date w/c 2026-08-24
*YP 5.0.17 Build Date 2026-03-16
 
*YP 5.0.17 Release Date 2026-03-23
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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:'''<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, 30 June 2026

Yocto Project Status 30 June 2026

Current Dev Position: YP 6.1 M2
Next Deadline: YP 6.1 M2: w/c 2026-07-20

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.1 M1 was released
  • YP 6.0.2 is in QA
  • The number of open CVEs on scarthgap has been reduced with stable kernel updates merging. We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases, see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
  • Systemd v260+ will require a host Linux kernel of 5.10 or later due to systemd utils run during the build process. This presents issues with RHEL 8 era distros which have older kernel versions. We have patches in progress but if you’re using these distros, assistance will be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
  • We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
  • 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
  • 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

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2:
    • Build Date: w/c 2026-07-20
    • Release Date: w/c 2026-08-03
  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 5.0.19
    • Build Date w/c 2026-06-30
    • Release Date w/c 2026-07-13
  • YP 6.0.3
    • Build Date w/c 2026-08-10
    • Release Date w/c 2026-08-24

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