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 17 February 2026 (WW08)
Date: Tue, 17 Feb 2026 15:52:42 +0000 [thread overview]
Message-ID: <207c307fe05f93e3f12a39fb93dab0cbdd77b6bf.camel@pbarker.dev> (raw)
[-- Attachment #1: Type: text/plain, Size: 5348 bytes --]
Hi all,
Current Dev Position: YP 6.0 M2
Next Deadline: YP 6.0 M2 Build Date 2026-02-16
Next Team Meetings:
- Bug Triage meeting - Thursday 19th Feb. 7:30am PDT
(https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT
(https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT
(https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
Project data dashboard: https://dashboard.yoctoproject.org/
Key Status/Updates:
- YP 4.0.33 is awaiting approval
- YP 5.0.16 is in QA
- YP 6.0 M2 is due to build this week but is blocked by high priority
bugs
- There are currently 5 high open bugs, which will block M2. Three have
line of sight to being resolved:
- rust do_test_compile/do_install segfault (#16058)
- Generation of releases.json needs updating (#16138)
- AB-INT: do_image_wic: tar command return exit status 2 (#16143)
- Two are currently needing further work:
- x86 kvm broken on Fedora 43 (#16074)
- AB-INT: opkg-build segmentation fault (#16078)
- We removed the bazaar, osc and cvs fetchers since they are obsolete
and nobody should be using them
- We removed sysvinit compatibility support from systemd images since
this will not be supported by upstream during the lifespan of our
upcoming LTS release.
- We removed legacy tls support from openssl in the interests of
providing better secure defaults.
- The number of intermittent failures affecting builds, both stable and
development, continues to be problematic - we continue to prioritise
addressing these since any given build is now statistically likely to
hit one or more of them.
- Patch review is now using two branches:
- “master-review” - patches which pass on the autobuilder and will
be discussed on the patch review call
(https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
- “master-backlog” - patches which have been discussed and need
further investigation or more detailed feedback which we haven’t
had time for yet
(https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
- Patches are merging 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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
- OE-Core/Poky Patch Metrics
- Total patches found: 1108 (last week 1106)
- Patches in the Pending State: 151 (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-16
- YP 6.0 M2 Release Date 2026-02-27
- YP 6.0 M3 Build Date 2026-03-09
- YP 6.0 M3 Release Date 2026-03-20
- YP 6.0 M4 Build Date 2026-03-30
- YP 6.0 M4 Release Date 2026-04-26
Upcoming dot releases:
- 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
[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
reply other threads:[~2026-02-17 15:52 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=207c307fe05f93e3f12a39fb93dab0cbdd77b6bf.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