Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(89 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Dec. 10th, 2024 ==
== Yocto Project Status 2 June 2026 ==
Current Dev Position: YP 5.2 M1<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<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 Dec. 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 4th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Dec. 10th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 2nd June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 4th June 10am GMT and Monday 8th June 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/>
*We are due to build YP 5.2 M1 this week
*YP 5.0.18 is due to be released
*YP 5.1.1 is due to be released
*YP 6.0.1 is in QA.
*There will be a status report next week (17th) but then not until 7th January due to holidays.
*YP 6.1 M1 is due to build next week
*Thanks to everyone who attended, presented, organized or was otherwise involved with the summit last week, there was lots of positive feedback!
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Parts of the bitbake fragments support has merged with some minor discussions pending for the rest.
*The upgrade to gcc 16 merged
*We hope to get the fragments support merged for the M1 build but we’ve run of out time for the clang patches.
*We are planning to improve our python subprocess calls to avoid shell=True, we would appreciate others following and doing this in their code too.
*There are discussions around how the yocto-check-layer script should verify network access is being enabled when it shouldn’t be (basically do_build triggered tasks which aren’t do_fetch).
*Intermittent build failures continue to be problematic and unchanged from last week:
*The large number of kernel CVEs open continues to be a significant concern.
**several qemu ‘hang’ type issues
*rpm will have new dependencies on rust and clang to enable signing support.
**sometimes yocto-check-layer is showing checksum mismatch issues
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
**siggen reset issues (“ResourceWarning: unclosed transport”)
*We need to continue to develop this, thanks to all who have contributed so far!
**groff build race issues
**intermittent ptest failures in many recipes
*Qemu v11 dropped support for 32 bit hosts and we are likely to drop support for running builds on 32 bits hosts
*The upstream kernel is looking likely to drop x32 support and if they do, we will have to drop our support too - let hem/us know if you’re using it!
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto


'''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 2820 (last week 2791) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2630 (last week 2660) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1043 (last week 1066)
**Total patches found: 108 (last week 1083)
**Patches in the Pending State: 176 (17%) [last week 177 (17%)]
**Patches in the Pending State: 147 (14%) [last week 148 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
7
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.2 M1 Build Date 2024-12-09
*YP 5.2 M1 Release Date 2024-12-20
*YP 5.2 M2 Build Date 2025-01-20
*YP 5.2 M2 Release Date 2025-01-31
*YP 5.2 M3 Build Date 2025-03-03
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25
 
'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.1.1 is ready for release.
*YP 5.0.18 is in review.
*YP 5.0.6 Build Date 2024-12-16
*YP 6.0.1 is in QA.
*YP 5.0.6 Release Date 2024-12-27
*YP 6.0.2
*YP 4.0.24 Build Date 2025-01-06
**Build Date 2026-06-23
*YP 4.0.24 Release Date 2025-01-17
**Release Date 2026-07-06
*YP 5.1.2 Build Date 2025-01-13
*YP 5.0.19
*YP 5.1.2 Release Date 2025-01-24
**Build Date 2026-06-30
*YP 5.0.7 Build Date 2025-01-27
**Release Date 2026-07-13
*YP 5.0.7 Release Date 2025-02-07
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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 81: Line 58:


== 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:41, 2 June 2026

Yocto Project Status 2 June 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.0.18 is due to be released
  • YP 6.0.1 is in QA.
  • YP 6.1 M1 is due to build next week
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
  • The upgrade to gcc 16 merged
  • We are planning to improve our python subprocess calls to avoid shell=True, we would appreciate others following and doing this in their code too.
  • Intermittent build failures continue to be problematic and unchanged from last week:
    • several qemu ‘hang’ type issues
    • 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
  • Qemu v11 dropped support for 32 bit hosts and we are likely to drop support for running builds on 32 bits hosts
  • The upstream kernel is looking likely to drop x32 support and if they do, we will have to drop our support too - let hem/us know if you’re using it!
  • We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

Ways to contribute:

New to the project?

Tracking Metrics:

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