2026 Yocto Project Weekly Status Archive: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>
6
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we 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.
'''Ways to contribute:'''<br/>
*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?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
'''Tracking Metrics:'''<br/>
*WDD 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*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:'''<br/>
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*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:'''<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>
6
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we 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 plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
'''Ways to contribute:'''<br/>
*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?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
'''Tracking Metrics:'''<br/>
*WDD 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*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:'''<br/>
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*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:'''<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
== Yocto Project Weekly Status Jan. 6th, 2026 ==
== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1<br/>
Current Dev Position: YP 6.0 M1<br/>

Latest revision as of 16:06, 20 January 2026

Yocto Project Weekly Status Jan. 20th, 2026

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M1 Build Date 2026-01-05
6 Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.15 is under review.
  • YP 5.3.1 is in QA
  • YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
  • Good progress has been made with the autobuilder issues and builds now complete but contain failures.
  • There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
    • Hangs of the autobuilder controller (database locking?) (#16129)
    • Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
    • still need to disable the npm fetcher (#16105)
    • x86 kvm broken on Fedora 43 (#16074)
    • AB-INT: build-sysroots: useradd command did not succeed (#16135)
  • The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we 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.

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M1 Build Date 2026-01-05
  • YP 6.0 M1 Release Date 2026-01-16
  • 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.0.15 is under review.
  • YP 5.3.1 in QA.
  • YP 4.0.33 Build Date 2026-01-26
  • YP 4.0.33 Release Date 2026-01-30
  • 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

Yocto Project Weekly Status Jan. 13th, 2026

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M1 Build Date 2026-01-05
6 Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.15 is under review.
  • YP 5.3.1 is in QA
  • YP 6.0 M1 will build when the 5 open high bugs are resolved.
  • There are also 4 high bugs open for 6.0 M2.
  • We are seeing multiple serious issues blocking 6.0 M1 from building:
    • A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
    • Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
    • Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
    • Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
    • still need to disable the npm fetcher (#16105)
  • We have not had this number of high bugs blocking releases in several years
  • The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we 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 plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
  • To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
  • The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M1 Build Date 2026-01-05
  • YP 6.0 M1 Release Date 2026-01-16
  • 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.0.15 is under review.
  • YP 5.3.1 in QA.
  • YP 4.0.33 Build Date 2026-01-26
  • YP 4.0.33 Release Date 2026-01-30
  • 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

Yocto Project Weekly Status Jan. 6th, 2026

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M1 Build Date 2026-01-05
6 Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.15 is in QA
  • YP 6.0 M1 will build when the 5 open high bugs are resolved.
  • We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
  • Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
  • Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
  • The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
  • We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
  • The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
  • We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

Ways to contribute:

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M1 Build Date 2026-01-05
  • YP 6.0 M1 Release Date 2026-01-16
  • 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.0.15 in QA.
  • YP 5.3.1 Build Date 2026-01-12
  • YP 5.3.1 Release Date 2026-01-23
  • YP 4.0.33 Build Date 2026-01-26
  • YP 4.0.33 Release Date 2026-01-30
  • 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