Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(48 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Feb. 4th, 2025 ==
== Yocto Project Weekly Status Dec. 9th, 2025 ==
Current Dev Position: YP 5.2 M3<br/>
Current Dev Position: YP 5.3 M4 - Final Build QA and Release<br/>
Next Deadline: YP 5.2 M3 Build date 2025-03-03<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 Feb. 6th at 7:30 am PST (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 Project Engineering Sync Tuesday Feb. 4th at 8 am PST (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/>
*YP 4.0.24 was released
*YP 5.0.14 was released
*YP 5.2 M2 has completed QA and is under review.
*YP 5.3 rc4 has passed QA and is under review
*YP 5.0.7 was built and is ready for 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.
*We are now 4 weeks from feature freeze for 5.2
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*Patch flow has continued normally, many good fixes, some upgrades and kernel stable updates were merged.
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
*Issues were identified in gomod mirror handling which means the autobuilder meta-oe mirroring target now continually fails. We need to find a solution to this issue ASAP. The alternative is we drop meta-oe mirroring.
*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 plan to merge b4 configuration file support, thanks Quentin.
*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
*Due to issues with newer glibc and issues with the valgrind upgrade, we will drop valgrind ptest support since nobody can maintain it.
*Further bitbake-setup changes under discussion for the new development cycle:
*Toolchain selection via virtual recipe specific providers was merged
**defaulting to a common sstate directory and hashequiv server
*Patches for newer binutils, gdb and glibc are pending.
**Allowing symlinking of local existing repos into the build instead of fetching
*The binutils upgrade removes gold linker support so that will be removed from core.
*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!
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved
*We need to continue to develop this, thanks to all who have contributed so far!


'''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!
*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 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 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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*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/>
'''Tracking Metrics:'''<br/>
*WDD 2704 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1030)
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.2 Milestone Dates:'''<br/>
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.2 M2 is in review.
*YP 5.3 M4 in review for release.
*YP 5.2 M3 Build Date 2025-03-03
 
*YP 5.2 M3 Release Date 2025-03-14
'''YP 6.0 Milestone Dates:'''<br/>
*YP 5.2 M4 Build Date 2025-03-31
*YP 6.0 M1 Build Date 2026-01-05
*YP 5.2 M4 Release Date 2025-04-25
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.24 was released.
*YP 5.0.14 was released.
*YP 5.0.7 is in QA.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.25 Build Date 2025-02-17
*YP 4.0.32 Release Date 2025-12-24
*YP 4.0.25 Release Date 2025-02-28
*YP 5.0.15 Build Date 2026-01-05
*YP 5.1.3 Build Date 2025-02-24
*YP 5.0.15 Release Date 2026-01-16
*YP 5.1.3 Release Date 2025-03-07
*YP 5.3.1 Build Date 2026-01-12
*YP 5.0.8 Build Date 2025-03-10
*YP 5.3.1 Release Date 2026-01-23
*YP 5.0.8 Release Date 2025-03-21
*YP 4.0.33 Build Date 2026-01-26
*YP 5.1.4 Build Date 2025-03-24
*YP 4.0.33 Release Date 2026-01-30
*YP 5.1.4 Release Date 2025-04-04
*YP 5.0.16 Build Date 2026-02-09
*YP 4.0.26 Build Date 2025-04-07
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.26 Release Date 2025-04-18
*YP 5.3.2 Build Date 2026-02-16
*YP 5.0.9 Build Date 2025-04-21
*YP 5.3.2 Release Date 2026-02-27
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.34 Release Date 2026-03-06
*YP 4.0.27 Release Date 2025-05-30
*YP 5.3.3 Build Date 2026-03-09
*YP 5.0.10 Build Date 2025-06-02
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.10 Release Date 2025-06-13
*YP 5.0.17 Build Date 2026-03-16
*YP 4.0.28 Build Date 2025-06-30
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.28 Release Date 2025-07-11
*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/>

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"