Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Dec. 9th, 2025 ==
== Yocto Project Status 5 May 2026 ==
Current Dev Position: YP 5.3 M4 - Final Build QA and Release<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: YP 5.3 M4 Build Date 2025-11-10<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-22<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Dec. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 7th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 5th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 11th 10am GMT and Monday Dec. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Yocto Project Patch Review - Thursday 7th May 10am GMT and Monday 11th May 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.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.14 was released
*YP 4.0.35 was released
*YP 5.3 rc4 has passed QA and is under review
*YP 5.3.4 is due to release, pending TSC approval
*The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
*YP 6.0 is due to release, pending TSC approval
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
*Intermittent build failures continue to be problematic
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*Patch review/merging is slow due to public holidays clashing with a review call
*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
*Master is open for new development.
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*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 are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved


'''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 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2698 (last week 2788) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Total patches found: 1087 (last week 1085)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**Patches in the Pending State: 146 (13%) [last week 146 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.3 M4 in review for release.
 
'''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/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.14 was released.
*YP 5.3.4 is due to release, pending TSC approval
*YP 4.0.32 Build Date 2025-12-15
*YP 5.0.18
*YP 4.0.32 Release Date 2025-12-24
**Build Date 2026-05-11
*YP 5.0.15 Build Date 2026-01-05
**Release Date 2026-05-25
*YP 5.0.15 Release Date 2026-01-16
*YP 6.0.1
*YP 5.3.1 Build Date 2026-01-12
**Build Date 2026-05-18
*YP 5.3.1 Release Date 2026-01-23
**Release Date 2026-06-01
*YP 4.0.33 Build Date 2026-01-26
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 89: Line 49:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]

Revision as of 14:45, 5 May 2026

Yocto Project Status 5 May 2026

Current Dev Position: YP 6.1 M1
Next Deadline: YP 6.1 M1: w/c 2026-06-22

Next Team Meetings:

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

Key Status/Updates:

  • YP 4.0.35 was released
  • YP 5.3.4 is due to release, pending TSC approval
  • YP 6.0 is due to release, pending TSC approval
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
  • Intermittent build failures continue to be problematic
  • Patch review/merging is slow due to public holidays clashing with a review call
  • Master is open for new development.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming dot releases:

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=86820"