Yocto Project Status 3 February 2026 (WW06)

--=-xvJ/YDz0pzbXNt/tQta8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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 5th Feb. 7:30am PDT
  (https://zoom.us/j/454367603?pwd=3DZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Weekly Project Engineering Sync  - Tuesday 3rd Feb. 8am PDT
  (https://zoom.us/j/990892712?pwd=3DcHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Fe=
b. 9am PDT
  (https://zoom.us/j/97762397148?pwd=3D1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

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

Key Status/Updates:
- YP 5.3.1 is due to be released
- YP 6.0 M1 is in QA
- YP 4.0.33 is queued for QA after 6.0 M1
- YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us
  three weeks each for M3 (target date 9th March) and M4 (target build
  date 30th March).
- Good progress has been made with the autobuilder issues but we still
  don=E2=80=99t have the stability in builds we need for reliable project
  operations.
- There are currently 5 high open bugs, which will block M2. Three have
  line of sight to being resolved (Thanks Alex and Michael!):
    - Issues reusing binaries from fedora 42/43 on older systems (#16087)
    - Hangs of the autobuilder controller (database locking?) (#16129)
    - Generation of releases.json needs updating (#16138)
- Two are currently needing further work:=20
    - rust do_test_compile/do_install segfault (#16058)
    - x86 kvm broken on Fedora 43 (#16074)
- =E2=80=9Cbuild-sysroots: useradd command did not succeed=E2=80=9D (#16135=
) was fixed,
  thanks Adrian!
- 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=E2=80=99=
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=E2=80=99ve 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=3D661406&priority=
=3DHigh&priority=3DMedium%2B&product=3DPseudo&query_format=3Dadvanced&resol=
ution=3D---
- 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/incl=
ude/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_-9owFuCW=
bzgjOk/edit?usp=3Dsharing

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=3DNEWCOMER

Tracking Metrics:
- WDD 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.htm=
l)
- OE-Core/Poky Patch Metrics
    - Total patches found: 1100 (last week 1097)
    - 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-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.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=E2=80=99s 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

Best regards,

--=20
Paul Barker


--=-xvJ/YDz0pzbXNt/tQta8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----

iIcEABYKAC8WIQSzjPXf5Y1BDWhU2iCrY1Tsnbr0bgUCaYICyhEccGF1bEBwYmFy
a2VyLmRldgAKCRCrY1Tsnbr0buc8AQCN06mYXXdr8Iw0uI66M6DrU8FrODwmf1jj
+4av9Oo79AD/QJmO2zfmw2BKuWCpQUkg0JOSh8w22Lk4l+BtgNm8lwE=
=TjAM
-----END PGP SIGNATURE-----

--=-xvJ/YDz0pzbXNt/tQta8--