Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 11: Line 11:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0.15 is in QA
*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.
*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.
*There are also 4 high bugs open for 6.0 M2.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
*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
**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!
*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:'''<br/>
'''Ways to contribute:'''<br/>
Line 49: Line 54:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.15 in QA.
*YP 5.0.15 is under review.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 in QA.
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 4.0.33 Release Date 2026-01-30

Revision as of 15:53, 13 January 2026

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

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86754"