Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(108 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Oct. 8th,  2024 ==
== Yocto Project Status 28 July 2026 ==
Current Dev Position: YP 5.1 release built and awaiting release notes<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 5.1 M4 Release date 2024-10-25<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Oct. 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 30th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Oct. 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 28th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 30th July 10am GMT and Monday 3rd Aug. 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.0.4 is due to be released
*YP 5.0.19 has been released
*YP 5.1 rc1 (final release) is out of QA, the final work item is updating the documentation. Help to write and review release notes and migration guides is greatly appreciated.
*YP 6.1 M2 is out of QA and under review
*The situation with Fedora 41 and python 3.13 has improved. There are several bitbake fixes needed and one one for pseudo the posix_spawn function.
*Progress has been made with some of the AB-INT issues:
*The bb.exceptions module could use some attention from someone with appropriate python knowledge (it makes tracebacks pickleable).
**We identified a kernel issue likely causing the arm psplash boot hangs
*CVE emails are now reporting correctly again, thanks Steve.
**The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
*We can now compare the performance of the new autobuilder perf builds:
**Several pseudo issues were patched in a recent update
**https://autobuilder.yocto.io/pub/non-release/20241007-108/testresults/buildperf-alma8/perf-alma8_master_20241007210052_312488228a.html
**One infrastructure issue on a worker was corrected
**https://valkyrie.yocto.io/pub/non-release/20241008-2/testresults/buildperf-alma8/perf-alma8-vk_master_20241008030040_312488228a.html
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
*The performance workers are about twice the speed (but the performance workers were not normal worker nodes on the old system). rm_work adds about a minute to build times on a modern SSD system.
**Matchbox-wm segfault/xserver restart
*Migration to the new autobuilder is proceeding with regular users now encouraged to trigger builds on the new cluster to stress test and identify any issues.
**aarch64/x86-64 build host contamination/reproducibility issue
*We are having problems with the toaster tests failing after layer index updates for styhead. If anyone has knowledge of selenium CSS selectors we’d appreciate assistance!
    We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*For 5.2 it would be helpful to have rough development plans for areas of the project if anyone is able to help document a rough roadmap/plan for them. The following areas are known to be being or need working on:
*Some invasive LICENSE changes have merged into master:
**Autobuilder
**We now require the LICENSE field to match SPDX identifiers.  
**Binary Distro
**The build will issue warnings when this isn’t the case.
**Bitbake config fragments
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**Bitbake setup process/tooling
**CLOSED is no longer a valid value.  
**GUI screen shot QA test
**‘WITH’ license exceptions are now supported
**IDE Plugin development
Big thanks to Joshua for getting us to the point where we can finally clean this up!
**Layer Index
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
**Patchtest
*We continue to work on the backlog of patches which has slightly reduced.
**Security Tooling
*Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
**Swatbot
*Remaining intermittent build failures  of concern:
**Toaster
**other qemu ‘hang’ type issues on ARM
*If there are other areas we should have plans for, please let us know.
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**intermittent ptest failures in many recipes


'''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 2704 (last week 2749) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2689 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1067)
**Total patches found: 1021 (last week 1019)
**Patches in the Pending State: 176 (16%) [last week 176 (16%)]
**Patches in the Pending State: 141 (14%) [last week 144 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.1 M4 Release date 2024-10-25
*6.1 M2: out of QA.
**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


'''YP 5.2 Milestone Dates:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.2 M1 Build Date 2024-12-09
*YP 5.0.19 due to release
*YP 5.2 M1 Release Date 2024-12-20
**Release Date w/c 2026-07-13
*YP 5.2 M2 Build Date 2025-01-20
*YP 6.0.3
*YP 5.2 M2 Release Date 2025-01-31
**Build Date w/c 2026-08-10
*YP 5.2 M3 Build Date 2025-03-03
**Release Date w/c 2026-08-24
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.0.20
*YP 5.2 M4 Build Date 2025-03-31
**Build Date w/c 2026-08-17
*YP 5.2 M4 Release Date 2025-04-25
**Release Date w/c 2026-08-31


'''Upcoming dot releases:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 5.0.4 is due to be released.
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29
*YP 5.1.1 Build Date 2024-12-02
*YP 5.1.1 Release Date 2024-12-13
*YP 5.0.6 Build Date 2024-12-16
*YP 5.0.6 Release Date 2024-12-27
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*YP 5.0.7 Build Date 2025-01-27
*YP 5.0.7 Release Date 2025-02-07
*YP 4.0.25 Build Date 2025-02-17
*YP 4.0.25 Release Date 2025-02-28
*YP 5.1.3 Build Date 2025-02-24
*YP 5.1.3 Release Date 2025-03-07
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.8 Release Date 2025-03-21
*YP 5.1.4 Build Date 2025-03-24
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.26 Build Date 2025-04-07
*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 105: Line 80:


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

Latest revision as of 14:48, 28 July 2026

Yocto Project Status 28 July 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.19 has been released
  • YP 6.1 M2 is out of QA and under review
  • Progress has been made with some of the AB-INT issues:
    • We identified a kernel issue likely causing the arm psplash boot hangs
    • The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
    • Several pseudo issues were patched in a recent update
    • One infrastructure issue on a worker was corrected
  • There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue
   We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
  • 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 to Joshua for getting us to the point where we can finally clean this up!

  • Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
  • We continue to work on the backlog of patches which has slightly reduced.
  • Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2: out of QA.
    • 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=86857"