Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(176 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status November 21st, 2023 ==
== Yocto Project Status 9 June 2026 ==
Current Dev Position: YP 5.0 M1<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: 4th December 2023 YP 5.0 M1 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 November 23, 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 November 21st at 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)
<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.14 and YP 3.1.29 were released
*YP 4.2.4  has passed QA and under discussion pending release
*Toaster news:
**Testing for toaster is now starting to be enabled on the autobuilder although not all tests are currently passing and there are host specific issues.
**The ability to view existing builds is being extended to allow debugging use of toaster even if the original build didn’t use it
*In support of the above, BB_DEFAULT_EVENTLOG is being proposed as enabled by default in bitbake.conf so that an event log is stored for all builds. This could be useful for debugging outside of toaster in other tools too. There is a small performance/disk footprint overhead but this should be offset by the useful debug data.
*The length of builds (world and oe-selftest) continues to be a concern.
*When running the first nanbield stable series builds, our LTS maintainer remarked on being unable to get successful green builds. We did make significant improvements on the intermittent issues prior to release but clearly not enough unfortunately. Troubling issues include:
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15005 - parsing failure on ubuntu2004/debian11 systems, maybe python/pthreads related with host python
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15166 - debuginfod issues (Ross has some debugging improvements pending)
**Devtool “initial_rev” race issue, an example failure: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6082/steps/14/logs/stdio
**several intermittent pstest issues
*There have been several fixes for meta-openembedded reproducibility issues and fixes for mirroring/CVE reporting on stable release branches, thanks Yoann.


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


<br/>
'''Key Status/Updates:'''<br/>
*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:'''<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.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''Tracking Metrics:'''<br/>
*WDD 2655 (last week 2630) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1056 (last week 1087)
**Patches in the Pending State: 147 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.0 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*6.1 M1:
*YP 5.0 M1 Release date 2023/12/15
**Build Date: w/c 2026-06-08
*YP 5.0 M2 build date  2024/01/15
**Release Date: w/c 2026-06-22
*YP 5.0 M2 Release date 2024/01/24
*6.1 M2:
*YP 5.0 M3 build date  2024/02/19
**Build Date: w/c 2026-07-20
*YP 5.0 M3 Release date 2024/03/01
**Release Date: w/c 2026-08-03
*YP 5.0 M4 build date  2024/04/01
*6.1 M3:
*YP 5.0 M4 Release date 2024/04/30
**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 3.1.29 build date 2023/10/30
*YP 6.0.1 is in QA.
*YP 3.1.29 Release date 2023/11/10
*YP 6.0.2
*YP 4.0.14 build date 2023/11/06
**Build Date w/c 2026-06-23
*YP 4.0.14 Release date 2023/11/17
**Release Date w/c 2026-07-06
*YP 4.2.4 build date 2023/11/13
*YP 5.0.19
*YP 4.2.4 Release date 2023/11/24
**Build Date w/c 2026-06-30
*YP 4.3.1 build date 2023/11/27
**Release Date w/c 2026-07-13
*YP 4.3.1 Release date 2023/12/08
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29
*YP 4.3.2 build date 2024/01/08
*YP 4.3.2 Release date 2024/01/19
*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/>
*WDD 2517 (last week 2533) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1177 (last week 1177)
**Patches in the Pending State: 253 (21%) [last week 253 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
 


'''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 96: 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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86838"