Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(112 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March 5th, 2024 ==
== Yocto Project Weekly Status Dec. 9th, 2025 ==
Current Dev Position: YP 5.0 M3 - Feature Freeze <br/>
Current Dev Position: YP 5.3 M4 - Final Build QA and Release<br/>
Next Deadline: 19th February 2024 YP 5.0 M3 build<br/>
Next Deadline: YP 5.3 M4 Build Date 2025-11-10<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday March 7th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Dec. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday March 5th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Dec. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Dec. 11th 10am GMT and Monday Dec. 13th 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 5.0, preparing to build M3
*YP 5.0.14 was released
*YP 4.3.3 was released
*YP 5.3 rc4 has passed QA and is under review
*YP 3.1.32 is in QA
*The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
*Several changes have merged for M3:
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
**genericarm64 machine (also added to autobuilder)
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
**go upgrade to 1.21.7
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
**rust upgrade to 1.75
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
**change to bmaptool hosting
*Further bitbake-setup changes under discussion for the new development cycle:
**using ipk to generate poky-altcfg images with extra space added
**defaulting to a common sstate directory and hashequiv server
**6.6.20 stable kernel update
**Allowing symlinking of local existing repos into the build instead of fetching
**ability to use “extratools” on autobuilder for tests (e.g. imagemagick components)
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*Changes still needed or under consideration
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved
**genericarm64 helper artefacts publishing changes
**QA screenshot comparison
**sstate permissions issue testcase
**go upgrade to 1.22 (tests cleanly on oe-core now, concerns for other layers)
*We are seeing some odd failures, there was a devtool selftest failure (bug 15418 filed) and also an opkg lock issue as we enabled ipk images but that hasn’t recurred (yet). The opkg lock issue has been seen in builds by Khem previously.
*There is a concerning problem when trying to update the CVE database since CPE restrictions don’t always update when changed upstream. This is causing higher numbers of CVEs to be reported on the autobuilder generated charts.
*There have been questions about official RISC-V support in this next release, especially since it is an LTS. We will trial qemuriscv64 support in M3 but remove it before the final LTS release as there is no sponsor for that support.


'''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 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*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 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.3 M4 in review for release.
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26


'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M3 build date  2024/02/19
*YP 5.0 M3 Release date 2024/03/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.3.3 was released.
*YP 5.0.14 was released.
*YP 3.1.32 is in QA.
*YP 4.0.32 Build Date 2025-12-15
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.32 Release Date 2025-12-24
*YP 4.0.17 build date 2024/03/11
*YP 5.0.15 Build Date 2026-01-05
*YP 4.0.17 Release date 2024/03/22
*YP 5.0.15 Release Date 2026-01-16
*YP 4.3.4 build date 2024/03/25
*YP 5.3.1 Build Date 2026-01-12
*YP 4.3.4 Release date 2024/04/05
*YP 5.3.1 Release Date 2026-01-23
*YP 3.1.33 build date 2024/04/15
*YP 4.0.33 Build Date 2026-01-26
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.33 Release Date 2026-01-30
*YP 4.0.18 build date 2024/04/22
*YP 5.0.16 Build Date 2026-02-09
*YP 4.0.18 Release date 2024/05/03
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.19 build date 2024/06/03
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.19 Release date 2024/06/14
*YP 5.3.2 Release Date 2026-02-27
 
*YP 4.0.34 Build Date 2026-02-23
'''Tracking Metrics:'''<br/>
*YP 4.0.34 Release Date 2026-03-06
*WDD 2618 (last week 2633) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.3.3 Build Date 2026-03-09
*OE-Core/Poky Patch Metrics
*YP 5.3.3 Release Date 2026-03-20
**Total patches found: 1155 (last week 1144)
*YP 5.0.17 Build Date 2026-03-16
**Patches in the Pending State: 249 (22%) [last week 250 (22%)]
*YP 5.0.17 Release Date 2026-03-23
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05


'''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 89:


== Archives ==
== Archives ==
*[[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 15:50, 9 December 2025

Yocto Project Weekly Status Dec. 9th, 2025

Current Dev Position: YP 5.3 M4 - Final Build QA and Release
Next Deadline: YP 5.3 M4 Build Date 2025-11-10

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.14 was released
  • YP 5.3 rc4 has passed QA and is under review
  • The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
  • There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
  • Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
  • Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
  • We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
  • Further bitbake-setup changes under discussion for the new development cycle:
    • defaulting to a common sstate directory and hashequiv server
    • Allowing symlinking of local existing repos into the build instead of fetching
  • The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
  • We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M4 in review for release.

YP 6.0 Milestone Dates:

  • YP 6.0 M1 Build Date 2026-01-05
  • YP 6.0 M1 Release Date 2026-01-16
  • YP 6.0 M2 Build Date 2026-02-02
  • YP 6.0 M2 Release Date 2026-02-13
  • YP 6.0 M3 Build Date 2026-03-02
  • YP 6.0 M3 Release Date 2026-03-13
  • YP 6.0 M4 Build Date 2026-03-30
  • YP 6.0 M4 Release Date 2026-04-26


Upcoming dot releases:

  • YP 5.0.14 was released.
  • 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
  • YP 5.3.1 Build Date 2026-01-12
  • YP 5.3.1 Release Date 2026-01-23
  • YP 4.0.33 Build Date 2026-01-26
  • YP 4.0.33 Release Date 2026-01-30
  • YP 5.0.16 Build Date 2026-02-09
  • YP 5.0.16 Release Date 2026-02-20
  • YP 5.3.2 Build Date 2026-02-16
  • YP 5.3.2 Release Date 2026-02-27
  • YP 4.0.34 Build Date 2026-02-23
  • YP 4.0.34 Release Date 2026-03-06
  • YP 5.3.3 Build Date 2026-03-09
  • YP 5.3.3 Release Date 2026-03-20
  • YP 5.0.17 Build Date 2026-03-16
  • YP 5.0.17 Release Date 2026-03-23
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-17
  • YP 5.3.4 Build Date 2026-04-13
  • YP 5.3.4 Release Date 2026-04-24
  • YP 5.0.18 Build Date 2026-04-20
  • YP 5.0.18 Release Date 2026-05-01
  • YP 5.0.19 Build Date 2026-05-26
  • YP 5.0.19 Release Date 2026-06-05

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=86729"