Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(88 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Feb. 11th, 2025 ==
== Yocto Project Status 21 July 2026 ==
Current Dev Position: YP 5.2 M3<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 5.2 M3 Build date 2025-03-03<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Feb. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 23rd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.2 M2 was released
*YP 6.0.2 has been released
*YP 5.0.7 is under review and passed QA
*YP 5.0.19 is due to release
*We are now 3 weeks from feature freeze for 5.2
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*The project autobuilder has upgraded the controller to buildbot 4.2 which was tricky due to our custom plugin and changes to the framework used for the UI. The new UI should have the same functionality and seems faster and easier to use in places.
*Some invasive LICENSE changes have merged into master:
*We’d like to request help to process the open github pull requests for openembedded-core and bitbake:
**We now require the LICENSE field to match SPDX identifiers.  
**https://github.com/openembedded/openembedded-core/pulls
**The build will issue warnings when this isn’t the case.
**https://github.com/openembedded/bitbake/pulls
**Non SPDX licenses will need to be of the form LicenseRef-XXX
*Having these open doesn’t look good for the projects and we can’t disable them, some have been open for a long time. We did already clean up the poky pull requests.
**CLOSED is no longer a valid value.  
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
**‘WITH’ license exceptions are now supported
*There are multiple occasional but annoying autobuilder failures we could do with help debugging/fixing, summarized by https://valkyrie.yocto.io/pub/non-release/abint/ :
Big thanks for Joshua for getting us to the point where we can finally clean this up!
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
***https://bugzilla.yoctoproject.org/show_bug.cgi?id=15463
*A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
**dnf failures in where ssh appears to fail, usually on qemumips but also seen on qemuarm: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13674
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
**Ongoing CDN failures
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
**New memory allocation issues hinting we may need to scale builds back
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
*We are open to help developing patches to help debug issue further or other ideas on the causes and/or ways to mitigate them
**several qemu ‘hang’ type issues on ARM
*The Linux Foundation published information on navigating global regulations and sanctions: https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions
**sometimes yocto-check-layer is showing checksum mismatch issues
*Please contact TSC members if there are questions/concerns.
**siggen reset issues (“ResourceWarning: unclosed transport”)
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.
**groff build race issues
*Gold linker support was removed from core.
**intermittent ptest failures in many recipes
*Linux 6.6 was removed so we now just have the 6.12 kernel we plan to release YP 5.2 with.
*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.
*The performance metric charts were improved to be able to show both commit based and time based data, allowing performance changes to be isolated more easily.
*The triage team decided to clear out the “newcomer” bugs in bugzilla since the remaining ones were likely too hard without specialist knowledge. We’d love to see new/realist newcomer bugs being added.
*The 5.2 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, thanks to all who have contributed so far!


'''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://wiki.yoctoproject.org/wiki/Newcomers
*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.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_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.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2711 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1025 (last week 1029)
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 172 (17%) [last week 173 (17%)]
**Patches in the Pending State: 144 (14%) [last week 145 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.2 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.2 M2 was released.
*6.1 M2:
*YP 5.2 M3 Build Date 2025-03-03
**Build Date: w/c 2026-07-20
*YP 5.2 M3 Release Date 2025-03-14
**Release Date: w/c 2026-08-03
*YP 5.2 M4 Build Date 2025-03-31
*6.1 M3:
*YP 5.2 M4 Release Date 2025-04-25
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.7 is in review.
*YP 5.0.19 due to release
*YP 4.0.25 Build Date 2025-02-17
**Release Date w/c 2026-07-13
*YP 4.0.25 Release Date 2025-02-28
*YP 6.0.3
*YP 5.1.3 Build Date 2025-02-24
**Build Date w/c 2026-08-10
*YP 5.1.3 Release Date 2025-03-07
**Release Date w/c 2026-08-24
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.20
*YP 5.0.8 Release Date 2025-03-21
**Build Date w/c 2026-08-17
*YP 5.1.4 Build Date 2025-03-24
**Release Date w/c 2026-08-31
*YP 5.1.4 Release Date 2025-04-04
 
*YP 4.0.26 Build Date 2025-04-07
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


'''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 85: Line 77:


== 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:50, 21 July 2026

Yocto Project Status 21 July 2026

Current Dev Position: YP 6.1 M2
Next Deadline: YP 6.1 M2: w/c 2026-07-20

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0.2 has been released
  • YP 5.0.19 is due to release
  • YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
  • Some invasive LICENSE changes have merged into master:
    • We now require the LICENSE field to match SPDX identifiers.
    • The build will issue warnings when this isn’t the case.
    • Non SPDX licenses will need to be of the form LicenseRef-XXX
    • CLOSED is no longer a valid value.
    • ‘WITH’ license exceptions are now supported

Big thanks for Joshua for getting us to the point where we can finally clean this up!

  • We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
  • Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
  • A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
  • Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
    • We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
    • several qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • groff build race issues
    • intermittent ptest failures in many recipes
  • For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2:
    • Build Date: w/c 2026-07-20
    • Release Date: w/c 2026-08-03
  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 5.0.19 due to release
    • Release Date w/c 2026-07-13
  • YP 6.0.3
    • Build Date w/c 2026-08-10
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31

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