Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(142 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 5th, 2023 ==
== Yocto Project Weekly Status Sept. 9th, 2025 ==
Current Dev Position: YP 4.3 Feature Freeze<br/>
Current Dev Position: YP 5.3 M3<br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>
Next Deadline: YP 5.3 M3 Build Date 2025-09-01<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday September 7th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Sept. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday September 5th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Sept. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Sept. 11th 10am GMT and Monday Sept. 15th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now at feature freeze for 4.3.
*YP 5.2.3 is due to be released.
*YP 4.2.3 was released
*YP 5.0.12 is due to be released.
*The qemupcc issue was tracked down to the glibc 2.38 included in the new uninative version. Upgrading along the glibc stable branch appeared to resolve the issue. It seems ppc was worst affected as the emulation is slow.
*YP 5.3 M3 is due to build soon
*We’re hoping to have tracked down the numpy reproducibility issue to non-deterministic blas library queries but we didn’t definitively work out which system was introducing the issue so we can’t be sure it is resolved.
*We’re at feature freeze for YP 5.3
*We need to upgrade to qemu 8.1.0 for security fixes but it is broken for x86. If we backport fixes for that issue, mips virtio breaks. We’ve filed a bug upstream: https://gitlab.com/qemu-project/qemu/-/issues/1866
*Updates to the 6.16 kernel are pending before the 5.3 M3 build
*Patches have been resubmitted to radically alter the do_unpack process for license compliance reasons. The code is complex and hard to understand and will have a performance impact on builds as well as making things hard to debug. *The risk of not taking the changes is that for some legal departments, the SPDX data isn’t detailed enough. The compromise between performance and ease of use vs. legal requirements is a tough one. We don’t really want to have two codepaths either. Feedback/review on the series welcome.
*We aim to merge bitbake-setup before building 5.3 M3
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated. This means autobuilder changes before we build 5.3 M3.
*Due to the number of issues related to mips and ppc being encountered with few people interested in helping fix them, we are likely to reduce the amount of testing being done on those targets before release. If you’re using these targets please let us know as we’re likely to drop them if there are no users.
*Patch merging is continuing as long as the risk for the changes are low
*M3 will build when we have a resolution to the qemu 8.1.0 issue and ideally fixes for the intermittent ptest issues.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
**Ecosystem Engineering and Operations Lead
**Marta Rybczynska will be working on the security topic
**LTS Maintainer  - Steve Sakoman is retiring in April 2026 (full details pending)
**Alexander Kanvin will be working on the core workflow topic
**Savoir-faire Linux will be working on the toaster and VSCode topics
**BayLibre will be working on the patchtest and project tooling topics
**Michael Opdenacker (Bootlin) will be working on the binary distro topic
The other remaining topic areas should be announced soon.
We’d also note that Tim Orling (Konsulko) will be working on the layer index.


'''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!
*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!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 bugs that are currently unassigned for YP 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*There are bugs identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*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
*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.
*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.
*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  
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*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/>
*WDD 2835 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1111 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 4.3 Milestone Dates:'''<br/>
'''YP 5.3 Milestone Dates:'''<br/>
*YP 4.3 M3 build date  2023/08/28
*YP 5.3 M3 Build Date 2025-09-01
*YP 4.3 M3 Release date 2023/09/08
*YP 5.3 M3 Release Date 2025-09-12
*YP 4.3 M4 build date  2023/10/02
*YP 5.3 M4 Build Date 2025-10-06
*YP 4.3 M4 Release date 2023/10/27
*YP 5.3 M4 Release Date 2025-10-31


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.2.3 is released
*YP 5.2.3 is being reviewed for release.
*YP 3.1.28 build date 2023/09/18
*YP 5.0.12 is being reviewed for release.
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.13 build date 2023/09/25
*YP 4.0.30 Release Date 2025-10-03
*YP 4.0.13 Release date 2023/10/06
*YP 5.2.4 Build Date 2025-09-29
*YP 3.1.29 build date 2023/10/30
*YP 5.2.4 Release Date 2025-10-10
*YP 3.1.29 Release date 2023/11/10
*YP 5.0.13 Build Date 2025-10-13
*YP 4.0.14 build date 2023/11/06
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.14 Release date 2023/11/17
*YP 4.0.31 Build Date 2025-11-03
*YP 4.2.4 build date 2023/11/13
*YP 4.031 Release Date 2025-11-14
*YP 4.2.4 Release date 2023/11/24
*YP 5.0.14 Build Date 2025-11-17
*YP 3.1.30 build date 2023/12/11
*YP 5.0.14 Release Date 2025-11-28
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.15 build date 2023/12/18
*YP 4.0.32 Release Date 2025-12-24
*YP 4.0.15 Release date 2023/12/29
*YP 5.0.15 Build Date 2026-01-05
 
*YP 5.0.15 Release Date 2026-01-16
'''Tracking Metrics:'''<br/>
*WDD 2500 (last week 2500) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1185 (last week 1188)
**Patches in the Pending State: 254 (21%) [last week 258 (22%)]
*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 70: Line 69:


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

Latest revision as of 14:48, 9 September 2025

Yocto Project Weekly Status Sept. 9th, 2025

Current Dev Position: YP 5.3 M3
Next Deadline: YP 5.3 M3 Build Date 2025-09-01

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 5.2.3 is due to be released.
  • YP 5.0.12 is due to be released.
  • YP 5.3 M3 is due to build soon
  • We’re at feature freeze for YP 5.3
  • Updates to the 6.16 kernel are pending before the 5.3 M3 build
  • We aim to merge bitbake-setup before building 5.3 M3
  • This change will mean “poky” as a combo-layer repository will no longer be needed or updated. This means autobuilder changes before we build 5.3 M3.
  • Patch merging is continuing as long as the risk for the changes are low
  • There are a couple of open Yocto Project positions which we’re in the process of advertising:
    • Ecosystem Engineering and Operations Lead
    • LTS Maintainer - Steve Sakoman is retiring in April 2026 (full details pending)

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M3 Build Date 2025-09-01
  • YP 5.3 M3 Release Date 2025-09-12
  • YP 5.3 M4 Build Date 2025-10-06
  • YP 5.3 M4 Release Date 2025-10-31

Upcoming dot releases:

  • YP 5.2.3 is being reviewed for release.
  • YP 5.0.12 is being reviewed for release.
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives