Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(148 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 7th, 2024 ==
== Yocto Project Status 8 September 2026 ==
Current Dev Position: YP 5.1 M1 <br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<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 9th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 10th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday May 7th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 8st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*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/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1.33 has been released
* YP 5.0.20 is under review.
*YP 4.0.18 is due to be released
* YP 6.1 M3 is due to build and we are at feature freeze
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990 Please consider signing this to show support for those changes. Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
* There are issues with changes in bot/AI protection at github.com which are affecting our CI.
*The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.  
* Most M3 changes have merged, we want to mitigate the github issues before building M3.
*There are proposals on the openembedded-architecture list to rework how do_unpack works, switching it from WORKDIR to a new variable and changing some directory layout.  
* 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
*The introduction of UNPACKDIR has happened, maintainers should be able to improve their S=WORKDIR recipes (which should use S, not WORKDIR/UNPACKDIR) and fix the common use of WORKDIR in do_compile/do_install to access files from SRC_URI which should now be UNPACKDIR.
* 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.
*gcc 14 has patches pending thanks for Khem and Martin in particular. Merging the new gcc version is needed to generate new uninative tarballs to support Fedora 40 builds or any other distro using the new gcc version.
* 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 project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal.
** Matchbox-wm segfault/xserver restart
*Mailing list changes now mean any google hosted email accounts have the mailing list From: address rewritten. This had impacted our ability to handle patches but key maintainers now have workarounds for this.
** 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
*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:'''<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.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2720 (last week 2728) (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: 1125 (last week 1125)
**Total patches found: 1050 (last week 1039)
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
**Patches in the Pending State: 136 (13%) [last week 139 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 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 3.1.33 is released.
*YP 6.0.3 is in review.
*YP 4.0.18 is ready for release.
**Release Date w/c 2026-08-24
*YP 4.0.18 Release date 2024-05-03
*YP 5.0.20 is in QA.
*YP 5.0.1 Build Date 2024-05-13
**Release Date w/c 2026-08-31
*YP 5.0.1 Release Date 2024-05-24
*YP 6.0.4
*YP 4.0.19 build date 2024-06-03
**Build Date w/c 2026-09-28
*YP 4.0.19 Release date 2024-06-14
**Release Date w/c 2026-10-12
*YP 5.0.2 Build Date 2024-06-24
*YP 5.0.21
*YP 5.0.2 Release Date 2024-07-05
**Build Date w/c 2026-10-05
*YP 4.0.20 Build Date 2024-07-15
**Release Date w/c 2026-10-19
*YP 4.0.20 Release Date 2024-07-26
 
*YP 5.0.3 Build Date 2024-08-12
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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


'''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 74: 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: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"