Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(71 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 24th, 2025 ==
== Yocto Project Status 8 September 2026 ==
Current Dev Position: YP 5.3 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 5.3 M2 Build date 2025-07-21<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 June 26th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 10th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 24th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 8st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 26th 10am GMT and Monday June 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Yocto Project Patch Review - Thursday 10th Sept. 10am GMT and Monday 14th Sept. 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 5.3 M1 is in QA
* YP 5.0.20 is under review.
*Patches continue to merge into master for upgrades and fixes.
* YP 6.1 M3 is due to build and we are at feature freeze
*The UNPACKDIR layout changes merged. This has been disruptive for layers and it will take a while for changes to filter through various layers. It does set up better in the future with tools like devtool to avoid having lots of legacy layouts to support, and cleans up git recipes to be easier to write going forward.
* There are issues with changes in bot/AI protection at github.com which are affecting our CI.  
*To support this, the layer series was updated to whinlatter in core.
* Most M3 changes have merged, we want to mitigate the github issues before building M3.
*The clang build time and size increases continue to cause significant concern.
* There is a new meta-openjdk layer: https://github.com/amarula/meta-openjdk https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
*There are patches in progress for improving gomod support in devtool and the mirroring issue for gomod was resolved.The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
* 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.
*Support for BUILDHISTORY_RESET was removed as it was error prone and better handled on the CI side of integration.
* 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:
*OE-Core is adopting the use of glvnd for libGL abstraction
** Matchbox-wm segfault/xserver restart
*The initial RISC-V tune changes merged
** aarch64/x86-64 build host contamination/reproducibility issue
*Support for distro/machine selection with builtin fragments was added.
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.
*A section was added to the manual on primary and secondary architecture/feature support for Yocto Project: https://docs.yoctoproject.org/dev/ref-manual/yocto-project-supported-features.html
*Remaining intermittent build failures of concern:
*An email about this was sent to the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2162
**other qemu ‘hang’ type issues on ARM
*For M2, the following changes have been mentioned as possibilities:
**sometimes yocto-check-layer is showing checksum mismatch issues
**bitbake-setup
**intermittent ptest failures in many recipes
**wic split from OE-Core
*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!
**RISC-V tune changes (part 2)
**go/gomod fetcher changes
**switch classextend to use [filter] support from bitbake


'''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 2778 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2622 (last week 2612) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1093 (last week 1084)
**Total patches found: 1050 (last week 1039)
**Patches in the Pending State: 157 (14%) [last week 158 (19%)]
**Patches in the Pending State: 136 (13%) [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 in QSA.
*6.1 M3:
*YP 5.3 M2 Build Date 2025-07-21
**Build Date: w/c 2026-08-31
*YP 5.3 M2 Release Date 2025-08-01
**Release Date: w/c 2026-09-14
*YP 5.3 M3 Build Date 2025-09-01
*6.1.0:
*YP 5.3 M3 Release Date 2025-09-12
**Build Date (M4): w/c 2026-10-12
*YP 5.3 M4 Build Date 2025-10-06
**Release Date: w/c 2026-11-02
*YP 5.3 M4 Release Date 2025-10-31


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.28 Build Date 2025-06-30
*YP 6.0.3 is in review.
*YP 4.0.28 Release Date 2025-07-11
**Release Date w/c 2026-08-24
*YP 5.2.2 Build Date 2025-07-07
*YP 5.0.20 is in QA.
*YP 5.2.2 Release Date 2025-07-18
**Release Date w/c 2026-08-31
*YP 5.0.11 Build Date 2025-07-14
*YP 6.0.4
*YP 5.0.11 Release Date 2025-07-25
**Build Date w/c 2026-09-28
*YP 4.0.29 Build Date 2025-08-11
**Release Date w/c 2026-10-12
*YP 4.0.29 Release Date 2025-08-25
*YP 5.0.21
*YP 5.2.3 Build Date 2025-08-18
**Build Date w/c 2026-10-05
*YP 5.2.3 Release Date 2025-08-29
**Release Date w/c 2026-10-19
*YP 5.0.12 Build Date 2025-08-25
 
*YP 5.0.12 Release Date 2025-09-05
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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 89: Line 69:


== 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:41, 8 September 2026

Yocto Project Status 8 September 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:

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
  • Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

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 review.
    • Release Date w/c 2026-08-24
  • YP 5.0.20 is in QA.
    • 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=86874"