Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(163 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 9th, 2024 ==
== Yocto Project Status 16 June 2026 ==
Current Dev Position: YP 5.0 M2<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: 15th January 2024 YP 5.0 M2 build<br/>
Next Deadline: YP 6.1 M1: w/c 2026-07-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday January 11th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 18th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday January 9th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 16th June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 18th June 10am GMT and Monday 22nd 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/>
*YP 3.1.30, 4.0.15 and 5.0 M1 were released
*YP 6.0.1 is due for release
*YP 4.3.2 is in QA
*YP 6.1 M1 is in QA
*Rust was upgraded from 1.71.1 to 1.74.1 in master. 1.75 has reproducibility issues.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*We were able to remove all exclusions on reproducibility in OE-Core and it is once again 100% reproducible.
*An initial round of patches to remove shell=True subprocess usage in OE-Core have now merged
*The sstate-cache-management script was rewritten in python. It is possible there are regressions compared to the previous version, we’ll have to fix them as they’re identified.
*AUH is now running daily in incremental mode so we can avoid large batches of upgrade patches and spread them out as well as reacting more quickly to new upstream releases. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know.
*A workaround for the long standing autobuilder failures on debian11 and ubuntu 18.04 was identified by preloading libgcc. This is now applied for python 3.8 and 3.9 versions within bitbake.
*We’ve deliberately aimed to get up to date with the AUH success patches to better evaluate the ongoing upgrades.
*We have switched to the 6.6 linux kernel
*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
*There are patches proposing new “inherit_defer” syntax for bitbake to handle conditional inherits in a way more in keeping with user expectations. Please see the discussion on the openembedded-architecture list.
*Intermittent build failures continue to be problematic and unchanged from last week:
*Functions related to signature/hash debugging had an API change resulting in a need to update bitbake and OE-Core together to allow the functionality to be improved.
**several qemu ‘hang’ type issues - the qemu upgrade merged, at least some issues still occur
*Improvements to the CDN tests and signature debugging were merged which improve usability and also address intermittent autobuilder failures
**sometimes yocto-check-layer is showing checksum mismatch issues
*Regarding bugs, even if you can’t fix a bug, submitting a failing test case that can reproduce the issue significantly improves the chances it might get fixed.
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes (python3-click was tweaked)
*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: patchtest, layerindex, 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 are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
 
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M1 is released.
*YP 5.0 M2 build date  2024/01/15
*YP 5.0 M2 Release date 2024/01/24
*YP 5.0 M3 build date  2024/02/19
*YP 5.0 M3 Release date 2024/03/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30


'''Upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 3.1.30 is released.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.0.15 is released.
*YP 4.3.2 is in QA.
*YP 3.1.31 build date 2024/01/22
*YP 3.1.31 Release date 2024/02/02
*YP 4.0.16 build date 2024/01/29
*YP 4.0.16 Release date 2024/02/09
*YP 4.3.3 build date 2024/02/12
*YP 4.3.3 Release date 2024/02/23
*YP 3.1.32 build date 2024/03/04
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.33 build date 2024/04/15
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2562 (last week 2574) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2590 (last week 2655) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1171 (last week 1171)
**Total patches found: 1061 (last week 1056)
**Patches in the Pending State: 252 (22%) [last week 252 (21%)]
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming development releases:'''<br/>
*6.1 M1:
**Build Date: w/c 2026-06-08
**Release Date: w/c 2026-06-22
*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:'''<br/>
*YP 6.0.1 is due to release
*YP 6.0.2
**Build Date w/c 2026-06-23
**Release Date w/c 2026-07-06
*YP 5.0.19
**Build Date w/c 2026-06-30
**Release Date w/c 2026-07-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


'''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 73: Line 71:


== 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:47, 16 June 2026

Yocto Project Status 16 June 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0.1 is due for release
  • YP 6.1 M1 is in QA
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
  • An initial round of patches to remove shell=True subprocess usage in OE-Core have now merged
  • AUH is now running daily in incremental mode so we can avoid large batches of upgrade patches and spread them out as well as reacting more quickly to new upstream releases. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know.
  • We’ve deliberately aimed to get up to date with the AUH success patches to better evaluate the ongoing upgrades.
  • We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
  • Intermittent build failures continue to be problematic and unchanged from last week:
    • several qemu ‘hang’ type issues - the qemu upgrade merged, at least some issues still occur
    • 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 (python3-click was tweaked)
  • 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:

Upcoming development releases:

  • 6.1 M1:
    • Build Date: w/c 2026-06-08
    • Release Date: w/c 2026-06-22
  • 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:

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