Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(74 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 20th, 2025 ==
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 5.3 M1<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 5.3 M1 Build date 2025-06-09<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 May 22nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 20th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 22nd 10am GMT and Monday May 26th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.27 is in QA
*YP 6.0.3 is in QA.
*qemuriscv64, qemuriscv64-tc (toolchain) and qemuriscv64-ptest were added to default testing on the autobuilder
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*musl-qemuarm64 was also added to default testing
*For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
*The clang build time and size increases continue to cause significant concern.
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
*Due to many recent changes such as gcc and clang, patch counts have risen significantly. We now need to focus on finding ways to reduce the numbers of Pending and Inappropriate patches.
*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:
*Many good upgrades and fixes were merged to master.
**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.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*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.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2813 (last week 2791) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1104)
**Total patches found: 1028 (last week 1030)
**Patches in the Pending State: 158 (14%) [last week 159 (14%)]
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.3 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.3 M1 Build Date 2025-06-09
*6.1 M3:
*YP 5.3 M1 Release Date 2025-06-20
**Build Date: w/c 2026-08-31
*YP 5.3 M2 Build Date 2025-07-21
**Release Date: w/c 2026-09-14
*YP 5.3 M2 Release Date 2025-08-01
*6.1.0:
*YP 5.3 M3 Build Date 2025-09-01
**Build Date (M4): w/c 2026-10-12
*YP 5.3 M3 Release Date 2025-09-12
**Release Date: w/c 2026-11-02
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.27 is in QA.
*YP 6.0.3 is in QA.
*YP 5.2.1 Build Date 2025-05-26
**Release Date w/c 2026-08-24
*YP 5.2.1 Build Date 2025-06-06
*YP 5.0.20
*YP 5.0.10 Build Date 2025-06-02
**Build Date w/c 2026-08-17
*YP 5.0.10 Release Date 2025-06-13
**Release Date w/c 2026-08-31
*YP 4.0.28 Build Date 2025-06-30
*YP 6.0.4
*YP 4.0.28 Release Date 2025-07-11
**Build Date w/c 2026-09-28
*YP 5.2.2 Build Date 2025-07-07
**Release Date w/c 2026-10-12
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.21
*YP 5.0.11 Build Date 2025-07-14
**Build Date w/c 2026-10-05
*YP 5.0.11 Release Date 2025-07-25
**Release Date w/c 2026-10-19
*YP 4.0.29 Build Date 2025-08-11
 
*YP 4.0.29 Release Date 2025-08-25
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16


'''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 84: Line 68:


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

Latest revision as of 14:45, 25 August 2026

Yocto Project Status 25 August 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 6.0.3 is in QA.
  • YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
  • For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
  • AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
  • We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
  • 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.

  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 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 6.0.3 is in QA.
    • 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
  • YP 6.0.4
    • Build Date w/c 2026-09-28
    • Release Date w/c 2026-10-12
  • YP 5.0.21
    • Build Date w/c 2026-10-05
    • Release Date w/c 2026-10-19

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