Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(38 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Oct. 7th, 2025 ==
== Yocto Project Status 12 May 2026 ==
Current Dev Position: YP 5.3 M3<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: YP 5.3 M3 Build Date 2025-09-01<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Oct. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 14th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 12th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 9th 10am GMT and Monday Oct. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Yocto Project Patch Review - Thursday 14th May 10am GMT and Monday 18th 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 4.0.30 was released.
*YP 5.3.4 is due to release (has been approved)
*YP 5.2.4 is under review.
*YP 6.0 is due to release (has been approved)
*YP 5.3 M3 is due to build soon.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
*Intermittent build failures continue to be problematic
**Fixing a reproducibility problem in perf from 6.16
*We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
**Split of llvm from clang (patches ready and in testing)
*Master is open for new development
**Merging of bitbake-setup
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.
*Bitbake-setup is nearing being ready for merging, there is one oe-selftest related issue we need to resolve first. Apart from this it is running successfully on the autobuilder.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*The proposal to allow backporting of SPDX 3 support to scarthgap was accepted by the TSC, assuming tests are added and pass.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer  - Steve Sakoman is retiring in April 2026


'''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 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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 2884 (last week 2854) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2688 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1103)
**Total patches found: 1087 (last week 1087)
**Patches in the Pending State: 154 (14%) [last week 154 (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 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.30 was released.
*YP 5.3.4 is due to release
*YP 5.2.4 is ready for release.
*YP 5.0.18
*YP 5.0.13 Build Date 2025-10-13
**Build Date 2026-05-11
*YP 5.0.13 Release Date 2025-10-24
**Release Date 2026-05-25
*YP 4.0.31 Build Date 2025-11-03
*YP 6.0.1
*YP 4.031 Release Date 2025-11-14
**Build Date 2026-05-18
*YP 5.0.14 Build Date 2025-11-17
**Release Date 2026-06-01
*YP 5.0.14 Release Date 2025-11-28
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16


'''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 68: 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]]

Latest revision as of 14:45, 12 May 2026

Yocto Project Status 12 May 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3.4 is due to release (has been approved)
  • YP 6.0 is due to release (has been approved)
  • 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
  • We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
  • Master is open for new development
  • We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.

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