Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(82 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 16th, 2024 ==
== Yocto Project Weekly Status Dec. 2nd, 2025 ==
Current Dev Position: YP 5.1 M2 <br/>
Current Dev Position: YP 5.3 M4 - Final Build QA and Release<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<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 July 18th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Dec. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday July 16th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Dec. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Dec. 4th 10am GMT and Monday Dec. 8th 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.20 is in QA
*YP 5.0.14 is due to be released
*YP 5.1 M2 is due to be built now SPDX 3.0 has merged
*YP 5.3 rc4 is built and due to enter QA
*SPDX 3.0 has merged, thanks Joshua, Marta and everyone else who has worked on this.
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*We’ve chosen to make SPDX 3.0 the default since it is much more suited to what we do.
*There were a lot of problems encountered during the final 5.3 release build. Most of these should have been resolved.
*A number of QA checks were moved from WARN_QA to ERROR_QA. The intention is to allow recipes to be marked up with known issues rather than have builds with warnings people tend to ignore, or ideally have the issues fixed.
*Patches started to merge for master development again. Unfortunately there is breakage on the autobuilder, probably from issues arising from Fedora 43 binaries being incompatible with older distros. Until this is resolved, patch flow will be limited.
*If layers choose to change ERROR_QA, please do it on a per layer basis with an override, not globally,
*Further bitbake-setup changes under discussion for the new development cycle:
*An upcoming version of Yocto Project Compatible will require some subset of the ERROR_QA checks to be tested and passed for the layer to be compatible.
**defaulting to a common sstate directory and hashequiv server
*Debug optimization handling was changed, the DEBUG_FLAGS variable was dropped in favor of a new DEBUG_LEVELFLAG which allows distros to more easily change recipe debug levels, in particular to control size.
**Allowing symlinking of local existing repos into the build instead of fetching
*The autobuilder has been running into space issues and we analyzed space usage in a build. Patches are proposed to drop the debug symbols for on target llvm to reduce space usage (along with teaks to qemu and openssl) as the output size is effectively unusable currently. Further work on minimizing disk usage would be very welcome and there is a direct relationship with build speed too.
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.
*Autobuilder test result/output indexing has been moved to a specific autobuilder job so the work is more visible to all users (the ‘indexing’ builder). The script has been optimized and the output html cleaned up by Sovereign Tech *Fund sponsorship through their contractors: https://autobuilder.yocto.io/pub/non-release/
*Some larger patches still need help with review these would be appreciated:
**Improved CVE tooling from Marta
**kernel fitimage changes from Adrian
**bitbake-setup and configuration fragments from Alexander
*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
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc. We tested rust 1.78 with master and there is a long list of reported issues on the mailing list unfortunately. Rust 1.77 has a much smaller list of problems at least in initial testing.


'''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 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.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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 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 2787 (last week 2822) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2963 (last week 2953) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1075)
**Total patches found: 1080 (last week 1082)
**Patches in the Pending State: 178 (16%) [last week 178 (17%)]
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.3 M4 in QA.
 
'''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.1 Milestone Dates:'''<br/>
*YP 5.1 M2 Build date 2024-07-08
*YP 5.1 M2 Release date 2024-07-19
*YP 5.1 M3 Build date 2024-08-26
*YP 5.1 M3 Release date 2024-09-06
*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 4.0.20 is in QA
*YP 5.0.14 is ready for release.
*YP 5.0.3 Build Date 2024-08-12
*YP 4.0.32 Build Date 2025-12-15
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.32 Release Date 2025-12-24
*YP 4.0.21 Build Date 2024-09-09
*YP 5.0.15 Build Date 2026-01-05
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.15 Release Date 2026-01-16
*YP 5.0.4 Build Date 2024-09-23
*YP 5.3.1 Build Date 2026-01-12
*YP 5.0.4 Release Date 2024-10-04
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.22 Release Date 2024-10-25
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.5 Release Date 2024-11-22
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.23 Build Date 2024-11-18
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.23 Release Date 2024-11-29
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 69: Line 86:


== 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 16:11, 2 December 2025

Yocto Project Weekly Status Dec. 2nd, 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 is due to be released
  • YP 5.3 rc4 is built and due to enter QA
  • There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
  • There were a lot of problems encountered during the final 5.3 release build. Most of these should have been resolved.
  • Patches started to merge for master development again. Unfortunately there is breakage on the autobuilder, probably from issues arising from Fedora 43 binaries being incompatible with older distros. Until this is resolved, patch flow will be limited.
  • 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
  • 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 QA.

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 is ready for release.
  • 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=86724"