Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(31 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 13th, 2026 ==
== Yocto Project Status 7 July 2026 ==
Current Dev Position: YP 6.0 M1<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>
6
 
'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 9th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 7th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Yocto Project Patch Review - Thursday 9th July 10am GMT and Monday 13th 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 5.0.15 is in QA
*YP 6.1 M1 was released
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*YP 6.0.2 is in review
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*YP 5.0.19 is in QA
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*We are now two weeks away from M2!
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We are having some challenges with the autobuilder, both with an NFS server open file/lock build up of some kind causing slowdown and eventual halting of write operations and also a mkdir cache race issue. We are working to debug both issues but it is distracting from other work like patch review and new development (e.g. layer.conf format changes).
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..
*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.
*A key pseudo memory corruption issue when interacting with bash was identified and patches are being worked on for a new pseudo release to address this.
*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:'''<br/>
'''Ways to contribute:'''<br/>
Line 31: Line 40:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 3026 (last week 3011) (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: 1089 (last week 1092)
**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://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


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


'''Upcoming dot releases:'''<br/>
*YP 5.0.19 is in QA.
**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
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31


'''Upcoming dot releases:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*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 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:46, 7 July 2026

Yocto Project Status 7 July 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 review
  • YP 5.0.19 is in QA
  • We are now two weeks away from M2!
  • We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
  • We are having some challenges with the autobuilder, both with an NFS server open file/lock build up of some kind causing slowdown and eventual halting of write operations and also a mkdir cache race issue. We are working to debug both issues but it is distracting from other work like patch review and new development (e.g. layer.conf format changes).
  • Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
  • We have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
  • 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.
  • A key pseudo memory corruption issue when interacting with bash was identified and patches are being worked on for a new pseudo release to address this.
  • 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 is in QA.
    • 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
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives