Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 6th, 202 ==
== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1<br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>
6
6
'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*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/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0.15 is in QA
*YP 5.0.15 is under review.
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*YP 5.3.1 is in QA
*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.
*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
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
**Hangs of the autobuilder controller (database locking?) (#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 reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
*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!
**still need to disable the npm fetcher (#16105)
*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)..
**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/>
'''Ways to contribute:'''<br/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*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 is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*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/
*There are bugs identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*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.
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_Unassigned_Enhancements/Bugs
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
 
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
'''New to the project?'''<br/>
*Help us resolve CVE issues: CVE metrics
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


Line 51: Line 52:


'''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

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

Archives

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