Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 28 April 2026 ==
== Yocto Project Status 7 July 2026 ==
Current Dev Position: YP 6.0 M4<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 6.0 Release Date w/c 2026-05-04<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 30th Apr. 7:30am PDT (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 29th Apr. 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 30th Apr. 10am GMT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.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 4.0.35 is due to release
*YP 6.1 M1 was released
*YP 5.3.4 is in QA
*YP 6.0.2 is in review
*YP 6.0 rc1 is in QA
*YP 5.0.19 is in QA
*There will be no patch review on Monday 4th May due to public holidays.
*We are now two weeks away from M2!
*We continue to triage the CVEs being reported by the new tooling.
*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
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
*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).
*There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
*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.
*The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
*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.
*git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*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 but are trying to clear the backlog.
*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 33: Line 40:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2788 (last week 2790) (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: 1085 (last week 1078)
**Total patches found: 1036 (last week 1054)
**Patches in the Pending State: 146 (13%) [last week 147 (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/
'''Upcoming development releases:'''<br/>
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.35 is in review.
*YP 5.0.19 is in QA.
*YP 5.3.4 is in QA
**Release Date w/c 2026-07-13
**Release Date 2026-05-06
*YP 6.0.3
*YP 5.0.18
**Build Date w/c 2026-08-10
**Build Date   2026-05-11
**Release Date w/c 2026-08-24
**Release Date 2026-05-25
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31
 
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


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

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