Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(172 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 9th, 2024 ==
== Yocto Project Status 18 August 2026 ==
Current Dev Position: YP 5.0 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: 15th January 2024 YP 5.0 M2 build<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 January 11th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 20th Aug. 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 18th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 20th Aug. 10am GMT and Monday 24th Aug. 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.1 M3 is due in two weeks and this will be the feature freeze point for YP 6.1.
*YP 4.3.2 is in QA
*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.
*Rust was upgraded from 1.71.1 to 1.74.1 in master. 1.75 has reproducibility issues.
*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
*We were able to remove all exclusions on reproducibility in OE-Core and it is once again 100% reproducible.
*There have been locking changes with do_fetch/do_unpack within the bitbake fetcher to allow better performance of builds with shared DL_DIRs. There are also performance improvements to the handling of repeated ssl connection queries.
*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.
*There is discussion on the architecture list about how we could improve the fetcher, particularly around how recursion is handled in git submodules: https://lists.openembedded.org/g/openembedded-architecture/message/2416
*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 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.
*We have switched to the 6.6 linux kernel
*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:
*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.
**Matchbox-wm segfault/xserver restart
*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.
**aarch64/x86-64 build host contamination/reproducibility issue
*Improvements to the CDN tests and signature debugging were merged which improve usability and also address intermittent autobuilder failures
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.
*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.
*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: 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
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 5.0 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 5.0 M1 is released.
*WDD 2704 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0 M2 build date  2024/01/15
*OE-Core/Poky Patch Metrics
*YP 5.0 M2 Release date 2024/01/24
**Total patches found: 1030 (last week 1028)
*YP 5.0 M3 build date  2024/02/19
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
*YP 5.0 M3 Release date 2024/03/01
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 5.0 M4 build date  2024/04/01
 
*YP 5.0 M4 Release date 2024/04/30
'''Upcoming development releases:'''<br/>
*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/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.30 is released.
*YP 6.0.3 due to release
*YP 4.0.15 is released.
**Release Date w/c 2026-08-24
*YP 4.3.2 is in QA.
*YP 5.0.20
*YP 3.1.31 build date 2024/01/22
**Build Date w/c 2026-08-17
*YP 3.1.31 Release date 2024/02/02
**Release Date w/c 2026-08-31
*YP 4.0.16 build date 2024/01/29
*YP 6.0.4
*YP 4.0.16 Release date 2024/02/09
**Build Date w/c 2026-09-28
*YP 4.3.3 build date 2024/02/12
**Release Date w/c 2026-10-12
*YP 4.3.3 Release date 2024/02/23
*YP 5.0.21
*YP 3.1.32 build date 2024/03/04
**Build Date w/c 2026-10-05
*YP 3.1.32 Release date 2024/03/15
**Release Date w/c 2026-10-19
*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/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*WDD 2562 (last week 2574) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1171 (last week 1171)
**Patches in the Pending State: 252 (22%) [last week 252 (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 73: Line 69:


== 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:45, 18 August 2026

Yocto Project Status 18 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.1 M3 is due in two weeks and this will be the feature freeze point for YP 6.1.
  • 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 would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
  • There have been locking changes with do_fetch/do_unpack within the bitbake fetcher to allow better performance of builds with shared DL_DIRs. There are also performance improvements to the handling of repeated ssl connection queries.
  • There is discussion on the architecture list about how we could improve the fetcher, particularly around how recursion is handled in git submodules: https://lists.openembedded.org/g/openembedded-architecture/message/2416
  • 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.
  • 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 due to release
    • 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=86866"