Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 28 April 2026 ==
== Yocto Project Status 23 June 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 M1: 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 25th June 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 23rd June. 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 25th June 10am GMT and Monday 29th June 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.0.1 was released
*YP 5.3.4 is in QA
*YP 6.1 M1 is in review
*YP 6.0 rc1 is in QA
*AUH is now running daily in incremental mode. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know. Help is needed with resolving automatic update failures and getting the patches into a state where they can be accepted.
*There will be no patch review on Monday 4th May due to public holidays.
*CVE metrics are up on scarthgap & wrynose branches due to delays with kernel upgrades. We’ve had intermittent LTP failures, kconfig type changes, lttng build failures and new warnings in dmesg which we needed to handle. We’re working through this, help is needed to accelerate testing of future stable kernel upgrades.
*We continue to triage the CVEs being reported by the new tooling.
*Systemd v260 will require Linux 5.10 or later. We run some systemd utils on the host during the build, so this presents issues with RHEL 8 era distros which have older kernel versions. If you use one of these distros, assistance may be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
*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.
*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.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*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.
*Intermittent build failures continue to be problematic:
*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.
**several qemu ‘hang’ type issues
*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.
**sometimes yocto-check-layer is showing checksum mismatch issues
*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.
**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 36:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2788 (last week 2790) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2620 (last week 2590) (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: 1054(last week 1061)
**Patches in the Pending State: 146 (13%) [last week 147 (14%)]
**Patches in the Pending State: 145 (14%) [last week 146 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
'''Upcoming development releases:'''<br/>
*6.1 M1:
**Build Date: w/c 2026-06-08
**Release Date: w/c 2026-06-22
*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 6.0.1 is due to release
*YP 5.3.4 is in QA
*YP 6.0.2
**Release Date 2026-05-06
**Build Date w/c 2026-06-23
*YP 5.0.18
**Release Date w/c 2026-07-06
**Build Date   2026-05-11
*YP 5.0.19
**Release Date 2026-05-25
**Build Date w/c 2026-06-30
**Release Date w/c 2026-07-13
*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:50, 23 June 2026

Yocto Project Status 23 June 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0.1 was released
  • YP 6.1 M1 is in review
  • AUH is now running daily in incremental mode. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know. Help is needed with resolving automatic update failures and getting the patches into a state where they can be accepted.
  • CVE metrics are up on scarthgap & wrynose branches due to delays with kernel upgrades. We’ve had intermittent LTP failures, kconfig type changes, lttng build failures and new warnings in dmesg which we needed to handle. We’re working through this, help is needed to accelerate testing of future stable kernel upgrades.
  • Systemd v260 will require Linux 5.10 or later. We run some systemd utils on the host during the build, so this presents issues with RHEL 8 era distros which have older kernel versions. If you use one of these distros, assistance may 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 M1:
    • Build Date: w/c 2026-06-08
    • Release Date: w/c 2026-06-22
  • 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:

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