From: Paul Barker <paul@pbarker.dev>
To: yocto@lists.yoctoproject.org,
openembedded-core@lists.openembedded.org,
yocto-status@lists.yoctoproject.org
Subject: Yocto Project Status 27 January 2026 (WW05)
Date: Tue, 27 Jan 2026 14:39:39 +0000 [thread overview]
Message-ID: <dcd18fd1d50785e049d9f9508cce941cc657dead.camel@pbarker.dev> (raw)
[-- Attachment #1: Type: text/plain, Size: 4956 bytes --]
Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M2 Build Date 2026-02-02
Next Team Meetings:
- Bug Triage meeting - Thursday 29th Jan. 7:30am PDT
(https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT
(https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT
(https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
Project data dashboard: https://dashboard.yoctoproject.org/
Key Status/Updates:
- YP 5.0.15 was released
- YP 5.3.1 is under review
- YP 6.0 M1 is in QA
- YP 4.0.33 is queued for QA after 6.0 M1
- YP 6.0 M2 is due next week!
- Good progress has been made with the autobuilder issues and an M1
build is in QA but we still don’t have the stability in builds we need
for reliable project operations.
- There are currently 6 high open bugs, which will block M2:
- Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on
older systems (patchelf triggered?) (#16074, #16087)
- x86 kvm broken on Fedora 43 (#16074)
- AB-INT: build-sysroots: useradd command did not succeed (#16135)
- Hangs of the autobuilder controller (database locking?) (#16129)
- Generation of releases.json needs updating (#16138)
- The number of intermittent failures affecting builds, both stable and
development, continues to be problematic. Any given build is now
statistically likely to hit one or more of them and we often don’t
have successful builds. Since we struggle to get help in addressing
these, we need to change and start potentially blocking releases
(including stable/LTS) until these get addressed in some way. We are
holding some dedicated meetings to triage these and find ways of
removing the failures from our builds which may include reducing
testing.
- Patches are merging again but there is a backlog and we’ve had to
prioritize simpler changes. We continue to struggle for bandwidth for
changes needing in depth review/feedback. This could impact features
making it into the LTS.
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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
- OE-Core/Poky Patch Metrics
- Total patches found: 1097 (last week 1099)
- Patches in the Pending State: 152 (14%) [last week 152 (14%)]
https://valkyrie.yocto.io/pub/non-release/patchmetrics/
YP 6.0 Milestone Dates:
- YP 6.0 M2 Build Date 2026-02-02
- YP 6.0 M2 Release Date 2026-02-13
- YP 6.0 M3 Build Date 2026-03-02
- YP 6.0 M3 Release Date 2026-03-13
- YP 6.0 M4 Build Date 2026-03-30
- YP 6.0 M4 Release Date 2026-04-26
Upcoming dot releases:
- YP 5.3.1 is under review.
- YP 4.0.33 is queued for QA after 6.0 M1.
- 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:
https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
reply other threads:[~2026-01-27 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dcd18fd1d50785e049d9f9508cce941cc657dead.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto-status@lists.yoctoproject.org \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox