Hi all,

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

Next Team Meetings:
 • Bug Triage meeting - Thursday 25th June 7:30am PDT 
(_https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09_)
 • Weekly Project Engineering Sync  - Tuesday 23rd June. 8am PDT 
(_https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09__)_ 
<https://zoom.us/j/990892712>
 • 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/_ 

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_

Want to contribute? We would appreciate help with the following areas:
 • We have several open issues for pseudo and limited maintainer time to work 
on them. Help from someone familiar with systems programming in C would be 
greatly appreciated. 
_https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---_
 • There are a large number of intermittent failures on our autobuilder, any 
help with investigating, reproducing or solving these issues would be welcome! 
_https://valkyrie.yocto.io/pub/non-release/abint/_
 • Many recipes in openembedded-core would benefit from a new recipe 
maintainer. Please look at 
_https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc_
 and see if you can adopt any of the unassigned recipes.
 • For more ways to contribute, see 
_https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing_

New to the project?
 • We have a list of issues we think are good places to start contributing: 
_https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER_

Tracking Metrics:
 • WDD 2620 (last week 2590) (_https://wiki.yoctoproject.org/charts/combo.html_)
 • OE-Core/Poky Patch Metrics
   • Total patches found: 1054(last week 1061)
   • Patches in the Pending State: 145 (14%) [last week 146 (14%)]
   • _https://valkyrie.yocto.io/pub/non-release/patchmetrics/_

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:
 • YP 6.0.2
   • Build Date w/c 2026-06-23
   • Release Date w/c 2026-07-06
 • YP 5.0.19
   • 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_

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

The Status reports are now stored on the wiki at: 
_https://wiki.yoctoproject.org/wiki/Weekly_Status_

[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Best regards,
Paul Barker
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#239406): 
https://lists.openembedded.org/g/openembedded-core/message/239406
Mute This Topic: https://lists.openembedded.org/mt/119942095/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to