Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(260 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 10th, 2023 ==
== Yocto Project Status 9 June 2026 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: 23rd January 2023 YP 4.2 M2 Build<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 January 12th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 11th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday January 10th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 9th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 11th June 10am GMT and Monday 15th 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 4.2 M1 and YP 4.0.6 were released.
*YP 5.0.18 has been released
*Builds on the autobuilder are problematic at present due to connection losses with the controller machine. We understand the cause and will be migrating the controller to a new server/location in the next maintenance window to address this.
*YP 6.0.1 is in QA.
*A number of invasive bitbake changes have merged including a change to add threading to bitbake’s server/cooker. This will allow us to attempt to resolve various UI/server hang related open bugs and to improve the user experience, e.g. Ctrl+C handling. If people do see issues with hangs, please report them and include the tail end of the bitbake-cookerdaemon.log file.
*YP 6.1 M1 is due to build this week
*The bitbake cache changes to optionally include more hash debugging information did merge. This currently triggers only for the bitbake -S operations but once that mode is triggered for memory resident bitbake, it is “sticky” and will remain set until it unloads. We have seen some OOM issues on autobuilder workers which may be related to this, more debugging is needed to check on bitbake’s memory usage.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Automatic bitbake function library dependency code has also merged and is active. This should let us migrate class code to become library code for performance improvements.
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
*A bug in the layer.conf variable changes was identified which was causing re-parsing when it wasn’t necessary. A fix has been merged to address that.
*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
*The OE TSC decided in favour of adding export flag expansion despite the performance impact so that patch will be queued.
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
*We merged a number of neat rust improvements which add on target cargo support and added automated QA tests for this functionality so we can ensure it continues to work and doesn’t regress. Thanks Alex Kiernan, we hope to see more series like this one!
*Intermittent build failures continue to be problematic and unchanged from last week:
*CVE levels in master have improved but still need a little work
**several qemu ‘hang’ type issues
*The autobuilder maintenance window is moving from Friday to Monday.
**sometimes yocto-check-layer is showing checksum mismatch issues
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*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 4.2 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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 https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive


'''YP 4.2 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.2 M2 build date 2023/01/23
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.2 M2 Release date 2023/02/03
*YP 4.2 M3 build date 2023/02/20
*YP 4.2 M3 Release date 2023/03/03
*YP 4.2 M4 build date 2023/04/03
*YP 4.2 M4 Release date 2023/04/28
 
'''Upcoming dot releases:'''<br/>
*YP 4.1.2 built and in QA
*YP 4.1.2 Release date 2023/01/20
*YP 3.1.22 build date 2023/01/16
*YP 3.1.22 Release date 2023/01/27
*YP 4.0.7 build date 2023/01/30
*YP 4.0.7 Release date 2023/02/10
*YP 3.1.23 build date 2023/02/13
*YP 3.1.23 Release date 2023/02/24
*YP 4.0.8 build date 2023/02/27
*YP 4.0.8 Release date 2023/03/10
*YP 4.1.3 build date 2023/03/06
*YP 4.1.3 Release date 2023/03/17
*YP 3.1.24 build date 2023/03/20
*YP 3.1.24 Release date 2023/03/31
*YP 4.0.9 build date 2023/04/10
*YP 4.0.9 Release date 2023/04/21
*YP 4.1.4 build date 2023/05/01
*YP 4.1.4 Release date 2023/05/13
*YP 3.1.25 build date 2023/05/08
*YP 3.1.25 Release date 2023/05/19
*YP 4.0.10 build date 2023/05/15
*YP 4.0.10 Release date 2023/05/26


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2447 (last week 2457) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2655 (last week 2630) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1176 (last week 1189)
**Total patches found: 1056 (last week 1087)
**Patches in the Pending State: 281 (24%) [last week 282 (24%)]
**Patches in the Pending State: 147 (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 in QA.
*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 72: Line 70:


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

Latest revision as of 08:13, 9 June 2026

Yocto Project Status 9 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 has been released
  • YP 6.0.1 is in QA.
  • YP 6.1 M1 is due to build this week
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
  • Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
  • 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
  • We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
  • 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
  • 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