Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(38 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 14th, 2025 ==
== Yocto Project Weekly Status Sept. 9th, 2025 ==
Current Dev Position: YP 5.2 M2<br/>
Current Dev Position: YP 5.3 M3<br/>
Next Deadline: YP 5.2 M2 Release date 2025-01-20<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 Jan. 16th at 7:30 am PST (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 Project Engineering Sync Tuesday Jan. 14th at 8 am PST (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/>
*YP 5.2 M1 has two major QA issues, one for beaglebone and one for beagleplay
*YP 5.2.3 is due to be released.
**A potential fix merged for the first issue, the second remains unresolved, kernel stable upgrades did not fix it.
*YP 5.0.12 is due to be released.
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15703
*YP 5.3 M3 is due to build soon
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704
*We’re at feature freeze for YP 5.3
*YP 5.2 M2 is due to build next week and we haven’t resolved M1 yet!
*Updates to the 6.16 kernel are pending before the 5.3 M3 build
*YP 5.0.6 has been approved for release
*We aim to merge bitbake-setup before building 5.3 M3
*YP 5.1.2 and 4.0.24 are queued in QA
*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.
*There is some discussion about toolchain selection mechanisms via virtual/cross-cc providers on the architecture list which could help with clang integration.
*Patch merging is continuing as long as the risk for the changes are low
*There are discussions about how to implement “manifest” based fetchers to handle cargo, go and npm amongst others. We need to solve this problem in a way which everyone can work with but there is limited feedback or involvement in the patch review. Help is needed here to get this right and solve the long standing problems with these forms of software. Thanks to everyone already involved in the discussions.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
*We were able to upgrade rust to 1.81, thanks!
**Ecosystem Engineering and Operations Lead
*Various other key changes were merged (fragment handling fix, aclocal cleanup, qemu options fixes, flag ??= support, pytest improvements, deb multilib fixes and more)
**LTS Maintainer  - Steve Sakoman is retiring in April 2026 (full details pending)
*A native class extension fix merged but it may cause some wider metadata issues short term since new dependencies are being exposed.
*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 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 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/>
'''Tracking Metrics:'''<br/>
*WDD 2763 (last week 2840) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2835 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1037)
**Total patches found: 1111 (last week 1095)
**Patches in the Pending State: 174 (17%) [last week 175 (17%)]
**Patches in the Pending State: 156 (14%) [last week 155 (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 M1 in review.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.2 M2 Build Date 2025-01-20
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.2 M2 Release Date 2025-01-31
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.2 M3 Build Date 2025-03-03
*YP 5.3 M4 Release Date 2025-10-31
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.6 is ready for release.
*YP 5.2.3 is being reviewed for release.
*YP 4.0.24 is in QA.
*YP 5.0.12 is being reviewed for release.
*YP 5.1.2 is in QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 5.0.7 Build Date 2025-01-27
*YP 4.0.30 Release Date 2025-10-03
*YP 5.0.7 Release Date 2025-02-07
*YP 5.2.4 Build Date 2025-09-29
*YP 4.0.25 Build Date 2025-02-17
*YP 5.2.4 Release Date 2025-10-10
*YP 4.0.25 Release Date 2025-02-28
*YP 5.0.13 Build Date 2025-10-13
*YP 5.1.3 Build Date 2025-02-24
*YP 5.0.13 Release Date 2025-10-24
*YP 5.1.3 Release Date 2025-03-07
*YP 4.0.31 Build Date 2025-11-03
*YP 5.0.8 Build Date 2025-03-10
*YP 4.031 Release Date 2025-11-14
*YP 5.0.8 Release Date 2025-03-21
*YP 5.0.14 Build Date 2025-11-17
*YP 5.1.4 Build Date 2025-03-24
*YP 5.0.14 Release Date 2025-11-28
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.32 Release Date 2025-12-24
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.15 Release Date 2026-01-16
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86680"