Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(151 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 9th, 2024 ==
== Yocto Project Status 18 August 2026 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 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 April 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 April 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 4.3.4 is due to be released.
*YP 6.1 M3 is due in two weeks and this will be the feature freeze point for YP 6.1.
*YP 5.0 rc1 is now due to build when ready.
*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.
*All dunfell patches should have been sent now in preparation for an April 15 build. This will be the last release of dunfell.
*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.
*For 5.0, we are still hoping to switch the hash equivalence server before running the release build but that is the only remaining pending change. We do also still need documentation work for the release
*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.
*A new yocto-status mailing list has been created where we plan to send just the project weekly status reports and any other suitable updates on the project. This should help those who found the traffic of the other mailing lists too much.
*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 yocto-patches mailing list has been setup and patches that used to go to the yocto@ list will be migrating over to this new list, making yocto@ a bit more friendly for questions and discussions. Information in layers is being updated to reflect this.
*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 received some disappointing feedback from a key organization in the RISC-V ecosystem that the Yocto Project was not important and not worth funding. We will take this feedback into account.
*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:
*The “Binary Distro” work is now well underway and there are PR Server passthrough patches under review. The wiki page has had a number of policy/process proposals documented, at least as a first pass. Help is welcome to help improve these, or highlight where further documentation is needed.
**Matchbox-wm segfault/xserver restart
*We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet but using data directly from MITRE may help give partial information. These issues are making it hard to know what to include in the 5.0 release as it isn’t clear which changes are security related.
**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 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 M4 build date  2024/04/01
*WDD 2704 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0 M4 Release date 2024/04/30
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1028)
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 Proposed Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*6.1 M3:
*YP 5.1 M1 Release date 2024-05-31
**Build Date: w/c 2026-08-31
*YP 5.1 M2 Build date 2024-07-08
**Release Date: w/c 2026-09-14
*YP 5.1 M2 Release date 2024-07-19
*6.1.0:
*YP 5.1 M3 Build date 2024-08-26
**Build Date (M4): w/c 2026-10-12
*YP 5.1 M3 Release date 2024-09-06
**Release Date: w/c 2026-11-02
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.3.4 is released.
*YP 6.0.3 due to release
*YP 3.1.33 build date 2024-04-15
**Release Date w/c 2026-08-24
*YP 3.1.33 Release date 2024-04-26
*YP 5.0.20
*YP 4.0.18 build date 2024-04-22
**Build Date w/c 2026-08-17
*YP 4.0.18 Release date 2024-05-03
**Release Date w/c 2026-08-31
*YP 4.0.19 build date 2024-06-03
*YP 6.0.4
*YP 4.0.19 Release date 2024-06-14
**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


'''Upcoming Proposed dot releases:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 5.0.1 Build Date 2024-05-13
*YP 5.0.1 Release Date 2024-05-24
*YP 5.0.2 Build Date 2024-06-24
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.20 Release Date 2024-07-26
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29
 
'''Tracking Metrics:'''<br/>
*WDD 2696 (last week 2681) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1174 (last week 1173)
**Patches in the Pending State: 249 (21%) [last week 249 (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 82: 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"