Date: Tue, 30 Jun 2026 15:51:44 +0100
From: Paul Barker <paul@pbarker.dev>
Reply-To: yocto@lists.yoctoproject.org, paul@pbarker.dev
To: yocto@lists.yoctoproject.org,
openembedded-core@lists.openembedded.org,
yocto-status@lists.yoctoproject.org
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 2nd July 7:30am PDT
(_Launch Meeting - Zoom
<Launch Meeting - Zoom)
*
Weekly Project Engineering Sync - Tuesday 30th June 8am PDT
(_Launch Meeting - Zoom
<Launch Meeting - Zoom)_
<Launch Meeting - Zoom;
*
Yocto Project Patch Review - Thursday 2nd July 10am GMT and Monday
6th July 9am PDT
(_Launch Meeting - Zoom
<Launch Meeting - Zoom)
Project data dashboard: _https://dashboard.yoctoproject.org/_
<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:
_main@lists.yoctoproject.org | Home
<main@lists.yoctoproject.org | Home;
*
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
_main@lists.openembedded.org | Home
<main@lists.openembedded.org | Home;
*
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_ <http://git.openembedded.org/>&
_git.yoctoproject.org_ <http://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:
o
several qemu ‘hang’ type issues
o
sometimes yocto-check-layer is showing checksum mismatch issues
o
siggen reset issues (“ResourceWarning: unclosed transport”)
o
groff build race issues
o
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_
<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.
_Bug List
<Bug List;
*
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/_
<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_
<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
_How you can help Yocto Project - Google Docs
<How you can help Yocto Project - Google Docs;
New to the project?
*
We have a list of issues we think are good places to start
contributing:
_Bug List
<Bug List;
Tracking Metrics:
*
WDD 2647 (last week 2620)
(_Yocto Project
<Yocto Project)
*
OE-Core/Poky Patch Metrics
o
Total patches found: 1036 (last week 1054)
o
Patches in the Pending State: 145 (14%) [last week 145 (14%)]
o
_https://valkyrie.yocto.io/pub/non-release/patchmetrics/_
<https://valkyrie.yocto.io/pub/non-release/patchmetrics/>
Upcoming development releases:
*
6.1 M2:
o
Build Date: w/c 2026-07-20
o
Release Date: w/c 2026-08-03
*
6.1 M3:
o
Build Date: w/c 2026-08-31
o
Release Date: w/c 2026-09-14
*
6.1.0:
o
Build Date (M4): w/c 2026-10-12
o
Release Date: w/c 2026-11-02
Upcoming dot releases:
*
YP 5.0.19
o
Build Date w/c 2026-06-30
o
Release Date w/c 2026-07-13
*
YP 6.0.3
o
Build Date w/c 2026-08-10
o
Release Date w/c 2026-08-24
*
For future release dates, see
_Release calendar - Yocto Project
<https://wiki.yoctoproject.org/wiki/Release_calendar>
The Yocto Project’s technical governance is through its Technical
Steering Committee, more information is available at:
_TSC - Yocto Project
<https://wiki.yoctoproject.org/wiki/TSC>
The Status reports are now stored on the wiki at:
_Weekly Status - Yocto Project
<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